jos poortvliet wrote: > > It only takes one negatively nice'd proc to affect X adversely. > > Then, maybe, we should start nicing X again, like we did/had to do until a > few years ago? Or should we just wait until X gets fixed (after all, > development goes faster than ever)? Or is this really the scheduler's > fault?
It's not enough to renice X. You would have to renice it, and any app that needed fixed latency, to the same nice of the negatively nice'd proc, which defeats the purpose... 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/
