From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Jens Axboe <axboe@suse.de>, Con Kolivas <kernel@kolivas.org>,
Robert Love <rml@tech9.net>,
Peter Lundkvist <p.lundkvist@telia.com>,
akpm@digeo.com, mingo@elte.hu,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bad interactive behaviour in 2.5.65-66 (sched.c)
Date: 31 Mar 2003 10:46:22 +0200 [thread overview]
Message-ID: <1049100382.638.2.camel@teapot> (raw)
In-Reply-To: <5.2.0.9.2.20030331085710.01aa6d30@pop.gmx.net>
On Mon, 2003-03-31 at 09:05, Mike Galbraith wrote:
> > > I don't think it's really bad for system responsiveness. I think the
> >
> >What drugs are you on? 2.5.65/66 is the worst interactive kernel I've
> >ever used, it would be _embarassing_ to release a 2.6-test with such a
> >rudimentary flaw in it. IOW, a big show stopper.
>
> It's only horrible when you trigger the problems, otherwise it's wonderful.
With scheduler tunables (in -mm, for example), setting min_timeslice =
max_timeslice = 25 helps a lot with those problems (at least for me) :-)
> > > problem is just that the sample is too small. The proof is that simply
> > > doing sleep_time %= HZ cures most of my woes. WRT contest and it's
> >
> >Irk, that sounds like a really ugly bandaid.
>
> Nope, it's a really ugly _tourniquet_ ;-)
>
> >I'm wondering why the scheduler guys aren't all over this problem,
> >getting it fixed.
>
> I think they are.
I hope so ;-)
Felipe Alfaro Solana
Linux Registered User #287198
http://counter.li.org
next prev parent reply other threads:[~2003-03-31 8:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 21:32 Bad interactive behaviour in 2.5.65-66 (sched.c) Peter Lundkvist
2003-03-29 23:23 ` Robert Love
2003-03-30 1:21 ` Felipe Alfaro Solana
2003-03-30 2:05 ` Robert Love
2003-03-30 2:33 ` Con Kolivas
2003-03-30 2:46 ` Robert Love
2003-03-30 3:58 ` Tom Sightler
2003-03-30 5:23 ` Andrew Morton
2003-03-30 19:24 ` Tom Sightler
2003-04-01 1:41 ` Jeremy Fitzhardinge
2003-03-30 14:14 ` Jens Axboe
2003-03-30 21:06 ` Con Kolivas
2003-03-31 2:23 ` Mike Galbraith
2003-03-31 6:35 ` Jens Axboe
2003-03-31 7:05 ` Mike Galbraith
2003-03-31 8:46 ` Felipe Alfaro Solana [this message]
2003-03-31 8:54 ` Nick Piggin
2003-04-20 3:55 ` Mike Galbraith
2003-04-18 13:58 ` Mike Galbraith
2003-03-30 10:16 ` Felipe Alfaro Solana
2003-03-30 11:18 ` Mika Liljeberg
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=1049100382.638.2.camel@teapot \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=efault@gmx.de \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=p.lundkvist@telia.com \
--cc=rml@tech9.net \
/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