Ingo Molnar wrote: > * Ingo Molnar <[EMAIL PROTECTED]> wrote: > > > [...] but there are still some nice issues. > > > > > > Try running 3 chew.c's, then renicing one to -10, starves others for > > > some seconds while switching prio-level. Now renice it back to 10, > > > it starves for up to 45sec. > > > > ok - to make sure i understood you correctly: does this starvation > > only occur right when you renice it (when switching prio levels), and > > it gets rectified quickly once they get over a few reschedules? > > meanwhile i managed to reproduce it by following the exact steps you > described, and i've fixed the bug in my tree. Can you confirm that the > patch below fixes it for you too?
Seems like this fixed it. But I can still see these awful latency blips in the presence of negatively niced chew.c at -10 and two chew.c's at nice 0. This gets really bad when sched_granularity_ns >= 5,000,000. Thanks! -- Al - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
