Searched hist:"9 d94a278" (Results 1 – 8 of 8) sorted by relevance
| /TaskScheduler/SchedulerTests/Tests/ |
| H A D | GroupTests.cpp | 9d94a278 Mon Sep 05 14:48:24 GMT 2016 s.makeev_local <[email protected]> Completely remove WaitGroupAndYield
It was a bad architecture decision, WaitGroupAndYield cost too much to
work properly (global mutex per group). Anyway this behaviour could be
implemented through parent/child tasks and is much more natural for
architecture.
|
| H A D | WaitTests.cpp | 9d94a278 Mon Sep 05 14:48:24 GMT 2016 s.makeev_local <[email protected]> Completely remove WaitGroupAndYield
It was a bad architecture decision, WaitGroupAndYield cost too much to
work properly (global mutex per group). Anyway this behaviour could be
implemented through parent/child tasks and is much more natural for
architecture.
|
| /TaskScheduler/Scheduler/Include/ |
| H A D | MTFiberContext.h | 9d94a278 Mon Sep 05 14:48:24 GMT 2016 s.makeev_local <[email protected]> Completely remove WaitGroupAndYield
It was a bad architecture decision, WaitGroupAndYield cost too much to
work properly (global mutex per group). Anyway this behaviour could be
implemented through parent/child tasks and is much more natural for
architecture.
|
| H A D | MTThreadContext.h | 9d94a278 Mon Sep 05 14:48:24 GMT 2016 s.makeev_local <[email protected]> Completely remove WaitGroupAndYield
It was a bad architecture decision, WaitGroupAndYield cost too much to
work properly (global mutex per group). Anyway this behaviour could be
implemented through parent/child tasks and is much more natural for
architecture.
|
| H A D | MTScheduler.h | 9d94a278 Mon Sep 05 14:48:24 GMT 2016 s.makeev_local <[email protected]> Completely remove WaitGroupAndYield
It was a bad architecture decision, WaitGroupAndYield cost too much to
work properly (global mutex per group). Anyway this behaviour could be
implemented through parent/child tasks and is much more natural for
architecture.
|
| /TaskScheduler/Scheduler/Source/ |
| H A D | MTThreadContext.cpp | 9d94a278 Mon Sep 05 14:48:24 GMT 2016 s.makeev_local <[email protected]> Completely remove WaitGroupAndYield
It was a bad architecture decision, WaitGroupAndYield cost too much to
work properly (global mutex per group). Anyway this behaviour could be
implemented through parent/child tasks and is much more natural for
architecture.
|
| H A D | MTFiberContext.cpp | 9d94a278 Mon Sep 05 14:48:24 GMT 2016 s.makeev_local <[email protected]> Completely remove WaitGroupAndYield
It was a bad architecture decision, WaitGroupAndYield cost too much to
work properly (global mutex per group). Anyway this behaviour could be
implemented through parent/child tasks and is much more natural for
architecture.
|
| H A D | MTScheduler.cpp | 9d94a278 Mon Sep 05 14:48:24 GMT 2016 s.makeev_local <[email protected]> Completely remove WaitGroupAndYield
It was a bad architecture decision, WaitGroupAndYield cost too much to
work properly (global mutex per group). Anyway this behaviour could be
implemented through parent/child tasks and is much more natural for
architecture.
|