From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@digeo.com>,
Linus Torvalds <torvalds@transmeta.com>, <rml@tech9.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [patch] "HT scheduler", sched-2.5.63-B3
Date: Fri, 07 Mar 2003 09:34:02 +0100 [thread overview]
Message-ID: <5.2.0.9.2.20030307092747.00cf64b0@pop.gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0303070913370.5173-100000@localhost.localdom ain>
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
next prev parent reply other threads:[~2003-03-07 8:18 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 9:50 [patch] "HT scheduler", sched-2.5.63-B3 Ingo Molnar
2003-02-28 21:12 ` Andrew Morton
2003-02-28 21:23 ` Robert Love
2003-03-01 4:25 ` Andrew Morton
2003-03-06 3:20 ` Linus Torvalds
2003-03-06 7:45 ` Andrew Morton
2003-03-06 7:47 ` Ingo Molnar
2003-03-06 15:07 ` Linus Torvalds
2003-03-06 16:54 ` Ingo Molnar
2003-03-06 17:03 ` Linus Torvalds
2003-03-06 17:24 ` Ingo Molnar
2003-03-06 17:42 ` Linus Torvalds
2003-03-06 17:54 ` Ingo Molnar
2003-03-06 18:02 ` Linus Torvalds
2003-03-06 18:11 ` Ingo Molnar
2003-03-06 17:55 ` John Levon
2003-03-06 18:07 ` Linus Torvalds
2003-03-06 18:11 ` John Levon
2003-03-06 18:16 ` Linus Torvalds
2003-03-06 18:15 ` Ingo Molnar
2003-03-06 18:20 ` Linus Torvalds
2003-03-06 18:10 ` David S. Miller
2003-03-06 18:18 ` Ingo Molnar
2003-03-07 5:57 ` Ingo Molnar
2003-03-07 5:54 ` Shawn
2003-03-07 6:04 ` Ingo Molnar
2003-03-07 14:28 ` jlnance
2003-03-07 6:45 ` Aaron Lehmann
2003-03-07 6:50 ` Ingo Molnar
2003-03-07 7:00 ` Aaron Lehmann
2003-03-07 7:36 ` Ingo Molnar
2003-03-08 18:28 ` Aaron Lehmann
2003-03-07 7:00 ` Andrew Morton
2003-03-07 3:19 ` Horst von Brand
2003-03-06 15:37 ` Linus Torvalds
2003-03-06 16:01 ` Jeff Garzik
2003-03-06 16:51 ` Linus Torvalds
2003-03-06 17:11 ` Ingo Molnar
2003-03-06 17:52 ` jvlists
2003-03-06 18:27 ` Ingo Molnar
2003-03-07 8:15 ` Xavier Bestel
2003-03-06 23:18 ` Robert Love
2003-03-06 18:49 ` Alan Cox
2003-03-06 17:55 ` Linus Torvalds
2003-03-06 18:04 ` Ingo Molnar
2003-03-06 18:13 ` Martin J. Bligh
2003-03-06 18:26 ` Linus Torvalds
2003-03-08 0:05 ` Daniel Phillips
2003-03-06 17:58 ` Ingo Molnar
2003-03-06 17:17 ` Ingo Molnar
2003-03-06 18:06 ` Dimitrie O. Paun
2003-03-06 22:14 ` Martin J. Bligh
2003-03-06 22:31 ` Dimitrie O. Paun
2003-03-06 23:05 ` Robert Love
2003-03-06 23:33 ` Martin J. Bligh
2003-03-06 18:25 ` Alan Cox
2003-03-06 17:35 ` Linus Torvalds
2003-03-06 22:30 ` Eric Northup
2003-03-06 23:40 ` Martin J. Bligh
2003-03-07 0:02 ` Linus Torvalds
2003-03-07 0:09 ` Dimitrie O. Paun
2003-03-06 22:00 ` Bill Davidsen
2003-03-06 17:13 ` Ingo Molnar
2003-03-06 17:30 ` Linus Torvalds
2003-03-06 17:33 ` Ingo Molnar
2003-03-06 17:50 ` Ingo Molnar
2003-03-06 18:00 ` Linus Torvalds
2003-03-06 20:42 ` Andrew Morton
2003-03-06 22:18 ` Robert Love
2003-03-07 5:52 ` Ingo Molnar
2003-03-07 5:51 ` Shawn
2003-03-07 6:01 ` Ingo Molnar
2003-03-07 6:07 ` Andrew Morton
2003-03-07 6:15 ` Ingo Molnar
2003-03-07 10:19 ` Helge Hafting
2003-03-07 11:06 ` Ingo Molnar
2003-03-07 7:45 ` Mike Galbraith
2003-03-07 7:45 ` Ingo Molnar
[not found] ` <Pine.LNX.4.44.0303070842420.4572-100000@localhost.localdom ain>
2003-03-07 8:09 ` Mike Galbraith
2003-03-07 8:10 ` Andrew Morton
2003-03-07 8:26 ` Mike Galbraith
2003-03-07 8:15 ` Ingo Molnar
[not found] ` <Pine.LNX.4.44.0303070913370.5173-100000@localhost.localdom ain>
2003-03-07 8:34 ` Mike Galbraith [this message]
2003-03-07 8:31 ` Ingo Molnar
2003-03-06 22:03 ` Martin Waitz
2003-03-06 22:07 ` Robert Love
2003-03-06 22:35 ` Martin Waitz
2003-03-06 22:56 ` Robert Love
2003-03-06 23:27 ` Martin Waitz
2003-03-06 23:36 ` Robert Love
2003-03-07 10:39 ` Ingo Molnar
2003-03-07 10:27 ` Ingo Molnar
2003-03-06 6:58 ` [patch] "interactivity changes", sched-2.5.64-A4 Ingo Molnar
2003-03-06 10:00 ` Andrew Morton
2003-03-06 10:07 ` [patch] "interactivity changes", sched-2.5.64-A5 Ingo Molnar
2003-03-06 10:16 ` [patch] "HT scheduler", sched-2.5.63-B3 Chris Wedgwood
2003-03-06 10:18 ` Ingo Molnar
[not found] <5.2.0.9.2.20030307093435.01a8fe88@pop.gmx.net>
2003-03-07 9:30 ` Ingo Molnar
[not found] ` <Pine.LNX.4.44.0303071003060.6318-100000@localhost.localdom ain>
2003-03-07 9:38 ` Mike Galbraith
2003-03-10 19:53 Perez-Gonzalez, Inaky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.2.0.9.2.20030307092747.00cf64b0@pop.gmx.net \
--to=efault@gmx.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).