From: William Lee Irwin III <wli@holomorphy.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Con Kolivas <kernel@kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5.64-mm2->4 hangs on contest
Date: Mon, 10 Mar 2003 02:21:00 -0800 [thread overview]
Message-ID: <20030310102100.GD20188@holomorphy.com> (raw)
In-Reply-To: <5.2.0.9.2.20030310105217.00cd25b0@pop.gmx.net>
At 08:12 PM 3/10/2003 +1100, Con Kolivas wrote:
>> Contest uses a modified process load from irman so it exhibits similar
>> behaviour. Not sure what +12 actually tells me though :-(
On Mon, Mar 10, 2003 at 11:05:25AM +0100, Mike Galbraith wrote:
> Aha! No wonder your symptoms look so similar. +12 is just a magic number
> that works... found by trusty old trial and error method. What I wanted to
> see was if your hang would also go away with the same magic number, or if
> renicing with any value helped you at all.
At 08:12 PM 3/10/2003 +1100, Con Kolivas wrote:
>> My simplistic understanding is that the pipe task in process_load gets
>> constantly elevated as "interactive" by the new scheduler, and nothing else
>> ever happens.
On Mon, Mar 10, 2003 at 11:05:25AM +0100, Mike Galbraith wrote:
> Appears so. I can make it "work" by doing a dinky (butt ugly:) tweak in
> activate_task().
IMHO directed yields should attempt to prevent priority inversion but
not elevate priorities otherwise. I'd bug mingo about it.
-- wli
next prev parent reply other threads:[~2003-03-10 10:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5.2.0.9.2.20030310075720.00c832f8@pop.gmx.net>
2003-03-10 9:12 ` 2.5.64-mm2->4 hangs on contest Con Kolivas
2003-03-10 10:05 ` Mike Galbraith
2003-03-10 10:21 ` William Lee Irwin III [this message]
2003-03-10 10:29 ` Mike Galbraith
2003-03-10 10:27 ` Con Kolivas
2003-03-12 9:21 ` Mike Galbraith
2003-03-12 10:25 ` Con Kolivas
2003-03-12 10:37 ` Mike Galbraith
2003-03-12 11:19 ` Con Kolivas
2003-03-12 12:30 ` Mike Galbraith
2003-03-13 1:22 ` Con Kolivas
2003-03-13 3:39 ` Mike Galbraith
2003-03-13 4:31 ` Mike Galbraith
2003-03-10 10:31 ` Mike Galbraith
2003-03-10 10:31 ` Con Kolivas
2003-03-10 10:43 ` Mike Galbraith
2003-03-10 10:42 ` Con Kolivas
2003-03-10 10:54 ` Mike Galbraith
[not found] <fa.ie98jja.2hkdj6@ifi.uio.no>
[not found] ` <fa.j59micm.1fhqe9k@ifi.uio.no>
2003-03-10 12:43 ` Ed Tomlinson
2003-03-10 12:47 ` Con Kolivas
2003-03-10 13:41 ` Mike Galbraith
2003-03-10 13:41 ` Ed Tomlinson
2003-03-10 14:12 ` Mike Galbraith
2003-03-10 14:04 ` Mike Galbraith
2003-03-10 2:29 Con Kolivas
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=20030310102100.GD20188@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=efault@gmx.de \
--cc=kernel@kolivas.org \
--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