> > the "desktop tuning" of making the max timeslice==min timeslice. Try an
> > -mm kernel with the scheduler tunables patch and try playing with the
> > max timeslice. Most have found that <=25 will usually stop these skips.
> > The default max timeslice of 300ms is just too long for the desktop and
> > interactivity estimator.
> Heh, cool. I have the same patch in my tree too, fixed it without rebooting
> even ;-) Still a *tiny* bit of skipping, but infinitely better than it was.
Fixed without rebooting? You binary-patched
kernel or what?
-- Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/