> From: Mike Galbraith <efault@xxxxxx> > > Add a yield_to function to the scheduler code, allowing us to > give enough of our timeslice to another thread to allow it to > run and release whatever resource we need it to release. > > We may want to use this to provide a sys_yield_to system call > one day. At least I want. Ruby has GIL(giant interpreter lock). And giant lock naturally enforce an app to implement cooperative multithreading model. Therefore it has similar problem with your one. Python solved this issue by slowing lock mechanism (two pthread-cond wakeup each GIL releasing), but I don't want it. Also, If pthread_cond_signal() call sys_yield_to imlicitly, we can avoid almost Nehalem (and other P2P cache arch) lock unfairness problem. (probaby creating pthread_condattr_setautoyield_np or similar knob is good one) -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
