From: Mike Galbraith <efault@gmx.de>
To: Charles Baylis <cb-lkml@fish.zetnet.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.64-mm6, a new test case for scheduler interactivity problems
Date: Fri, 14 Mar 2003 16:46:10 +0100 [thread overview]
Message-ID: <5.2.0.9.2.20030314161055.00cf33d8@pop.gmx.net> (raw)
In-Reply-To: <5.2.0.9.2.20030314152115.00ce76b0@pop.gmx.net>
At 03:34 PM 3/14/2003 +0100, Mike Galbraith wrote:
>At 10:01 PM 3/13/2003 +0000, Charles Baylis wrote:
>>My test case tries to reproduce this by creating a number of tasks which
>>alternate between being 'interactive' and CPU hogs. On my Celery 333 laptop
>>it can sometimes cause skips with only 1 child, and is pretty much
>>guaranteed to cause skips with more child tasks.
>
>Greetings,
>
>Nice test case. I don't have sound capability on my linux box, but your
>test case makes it fail the window wiggle test horribly. I fiddled with
>it a bit, and convinced it to "stop doing that please". Does the attached
>(experimental butchery) help your box's sp-sp-speach im-p-p-pediment?
P.S. If you try this, change STARVATION_LIMIT from 1*HZ to
2*MAX_TIMESLICE. With that, I can run a make -j5 bzImage, irman with fixed
mem_load, thud 3 and kasteroids with no trouble at ALL on my 128mb
p3/500. The only time things get ugly is when memload fires up. It
allocates 72mb and scribbles to it... a bit much for a 128mb box with
_this_ load ;-) Even then, swapping like heck, kasteroids is playable most
of the time.
Without the patch, irman's process load starves everyone to death, and thud
3 utterly destroys interactivity. YMMV of course (it _is_ an experiment...
might even explode;)
-Mke
next prev parent reply other threads:[~2003-03-14 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 22:01 Charles Baylis
2003-03-14 14:34 ` Mike Galbraith
2003-03-14 15:46 ` Mike Galbraith [this message]
2003-03-14 9:57 Felipe Alfaro Solana
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.20030314161055.00cf33d8@pop.gmx.net \
--to=efault@gmx.de \
--cc=cb-lkml@fish.zetnet.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®