Got asked an interesting question by @matt77hias about why enkiTS doesn't use std::future in the API and I think my answer might be worth sharing:https://github.com/dougbinks/enkiTS/issues/27 …
-
The only way the wait in enkiTS should cause a deadlock is if you have two tasks waiting on each other. This is a programming error which would easily be found since the program would always deadlock.
Not quite. If you have 4 threads, it's likely that another thread calls wait() and picks up the dependent task, safely making sure that the originally waiting task doesn't deadlock. This is also why I always test on 1 thread in addition to coreCount threads.
-
-
That can't happen in enkiTS, or we're misunderstanding each other (easy on twitter). I also test on 1 to hardware thread count threads.
-
You're right about twitter. Hope this helps. In the two scenarios, depending on which core picks up Task D, a deadlock *may* occur. Certainly, one a single core it's almost guaranteed. This is why wait-with-assist is multithreading code smell.pic.twitter.com/NijYw9eL1j
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.