jlauro on 07 December 2008
| MisterBlonde said: Also the code responsible for scheduling execution of threads to idle cores can get bogged down like an overworked traffic cop. The more cores the more work for the thread scheduler, the more behind it gets, the more cycles get consumed. |
As it is now, large number of cores would be an issue... however, if you put the thread scheduler in hardware, then it can be done in once every clock cycle.
Basically allocating a thread has to also be in hardware, and not take any more time then otherwise calling a function.
