> Wouldn't having a single run queue lock still serialize the cpu's when > getting a thread to run? Don't we really need a per cpu run queue, and > then have a scheduler that puts threads on the cpu's run queues? Balancing run queues has overhead as well. From what I've seen having threads bouncing back and forth between the sleep queue and the run queue because sleep / wakeup is overused (see lockmgr) is a bigger deal right now. Moving to multiple run queues is inappropriate at this time. -KipReceived on Sun Oct 08 2006 - 23:18:19 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:01 UTC