From: Jens Axboe <axboe@suse.de>
To: Robert Love <rml@tech9.net>
Cc: Con Kolivas <kernel@kolivas.org>,
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
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: Sun, 30 Mar 2003 16:14:04 +0200 [thread overview]
Message-ID: <20030330141404.GG917@suse.de> (raw)
In-Reply-To: <1048992365.13757.23.camel@localhost>
On Sat, Mar 29 2003, Robert Love wrote:
> On Sat, 2003-03-29 at 21:33, Con Kolivas wrote:
>
> > Are you sure this should be called a bug? Basically X is an interactive
> > process. If it now is "interactive for a priority -10 process" then it should
> > be hogging the cpu time no? The priority -10 was a workaround for lack of
> > interactivity estimation on the old scheduler.
>
> Well, I do not necessarily think that renicing X is the problem. Just
> an idea.
I see the exact same behaviour here (systems appears fine, cpu intensive
app running, attempting to start anything _new_ stalls for ages), and I
definitely don't play X renice tricks.
It basically made 2.5 unusable here, waiting minutes for an ls to even
start displaying _anything_ is totally unacceptable.
--
Jens Axboe
next prev parent reply other threads:[~2003-03-30 14:03 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 [this message]
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
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=20030330141404.GG917@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--cc=felipe_alfaro@linuxmail.org \
--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