Messages in this thread | | | Date | Fri, 07 Mar 2003 09:34:02 +0100 | From | Mike Galbraith <> | Subject | Re: [patch] "HT scheduler", sched-2.5.63-B3 |
| |
At 09:15 AM 3/7/2003 +0100, Ingo Molnar wrote:
>On Fri, 7 Mar 2003, Mike Galbraith wrote: > > > I can (could with your earlier patches anyway) eliminate the X stalls by > > setting X junk to SCHED_FIFO. I don't have ram to plug in, but I'm as > > certain as I can be without actually doing so that it's not ram > > shortage. > >okay. Can you eliminate the X stalls with setting X priority to -10 or so >(or SCHED_FIFO - although SCHED_FIFO is much more dangerous). And how does >interactivity under the same load look like with vanilla .64, as compared >to .64+combo? First step is to ensure that the new changes did not >actually hurt interactivity.
Oh, it's definitely _much_ better than .virgin. I didn't mean to imply that damage was done ;-) With .virgin, I have a _heck_ of a time grabbing the build window to kill it. With combo, rodent jerkiness makes it hard to find/grab, and multisecond stalls are still there, but much improved.
-Mike
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |