From: Con Kolivas <kernel@kolivas.org>
To: Mike Galbraith <efault@gmx.de>
Cc: bert hubert <bert.hubert@netherlabs.nl>,
lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@osdl.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Peter Williams <pwil3058@bigpond.net.au>
Subject: Re: [patch][rfc] quell interactive feeding frenzy
Date: Thu, 13 Apr 2006 20:16:44 +1000 [thread overview]
Message-ID: <200604132016.45512.kernel@kolivas.org> (raw)
In-Reply-To: <1144914061.9352.25.camel@homer>
On Thursday 13 April 2006 17:41, Mike Galbraith wrote:
> This way also allowed me to eliminate the interactive agony of an array
> switch when at 100% cpu. Seems to work well. No more agony, only tiny
> pin pricks.
>
> Anyway, interested readers will find a copy of irman2.c, which is nice
> for testing interactive starvation, attached. The effect is most
> noticeable with something like bonnie, which otherwise has zero chance
> against irman2. Just about anything will do though. Trying to fire up
> Amarok is good for a chuckle. Whatever. (if anyone plays with irman2
> on 2.6.16 or below, call it with -S 1)
Comments.
> +repeat:
> + while ((idx = find_next_bit(bitmap, MAX_PRIO, idx)) < MAX_PRIO) {
...
> + goto repeat;
...
> + if (rq->nr_running > 1)
> + requeue_starving(rq, now);
An O(n) function in scheduler_tick is probably not the way to tackle this.
--
-ck
next prev parent reply other threads:[~2006-04-13 10:17 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 9:38 [patch][rfc] quell interactive feeding frenzy Mike Galbraith
2006-04-07 9:47 ` Andrew Morton
2006-04-07 9:52 ` Ingo Molnar
2006-04-07 10:57 ` Mike Galbraith
2006-04-07 11:00 ` Con Kolivas
2006-04-07 11:09 ` Mike Galbraith
2006-04-07 10:40 ` Mike Galbraith
2006-04-07 12:56 ` Con Kolivas
2006-04-07 13:37 ` Mike Galbraith
2006-04-07 13:56 ` Con Kolivas
2006-04-07 14:14 ` Mike Galbraith
2006-04-07 15:16 ` Mike Galbraith
2006-04-09 11:14 ` bert hubert
2006-04-09 11:39 ` Mike Galbraith
2006-04-09 12:14 ` bert hubert
2006-04-09 18:07 ` Mike Galbraith
2006-04-10 9:12 ` bert hubert
2006-04-10 10:00 ` Mike Galbraith
2006-04-10 14:56 ` Mike Galbraith
2006-04-13 7:41 ` Mike Galbraith
2006-04-13 10:16 ` Con Kolivas [this message]
2006-04-13 11:05 ` Mike Galbraith
2006-04-09 18:24 ` Mike Galbraith
2006-04-09 16:44 Al Boldi
2006-04-09 18:33 ` Mike Galbraith
2006-04-10 14:43 ` Al Boldi
2006-04-11 10:57 ` Con Kolivas
[not found] <200604112100.28725.kernel@kolivas.org>
2006-04-11 17:03 ` Fwd: " Al Boldi
2006-04-11 22:56 ` Con Kolivas
2006-04-12 5:41 ` Al Boldi
2006-04-12 6:22 ` Con Kolivas
2006-04-12 8:17 ` Al Boldi
2006-04-12 9:36 ` Con Kolivas
2006-04-12 10:39 ` Al Boldi
2006-04-12 11:27 ` Con Kolivas
2006-04-12 15:25 ` Al Boldi
2006-04-13 11:51 ` Con Kolivas
2006-04-14 3:16 ` Al Boldi
2006-04-15 7:05 ` Con Kolivas
2006-04-15 20:45 ` Al Boldi
2006-04-15 23:22 ` Con Kolivas
2006-04-16 6:02 ` Con Kolivas
2006-04-16 8:31 ` Al Boldi
2006-04-16 8:58 ` 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=200604132016.45512.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=bert.hubert@netherlabs.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
/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;
as well as URLs for NNTP newsgroup(s).