From: Robert Love <rml@tech9.net>
To: Con Kolivas <kernel@kolivas.org>
Cc: 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: 29 Mar 2003 21:46:05 -0500 [thread overview]
Message-ID: <1048992365.13757.23.camel@localhost> (raw)
In-Reply-To: <200303301233.03803.kernel@kolivas.org>
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.
We do have a problem, though. Nearly indefinite starvation and all sort
of weird effects like bash not able to create a new process... its a
bug.
Renicing X, aside from some weird client-server starvation issues with
stuff like multimedia programs, should not cause any problem. It should
help, in fact. But, you are right, its not needed in the current
scheduler.
Robert Love
next prev parent reply other threads:[~2003-03-30 2:34 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 [this message]
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
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=1048992365.13757.23.camel@localhost \
--to=rml@tech9.net \
--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 \
/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