From: Mike Galbraith <efault@gmx.de>
To: MAEDA Naoaki <maeda.naoaki@jp.fujitsu.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
ckrm-tech@lists.sourceforge.net
Subject: Re: [ckrm-tech] Re: [PATCH 0/9] CPU controller
Date: Fri, 28 Apr 2006 12:01:09 +0200 [thread overview]
Message-ID: <1146218469.8067.25.camel@homer> (raw)
In-Reply-To: <1146216552.8067.11.camel@homer>
On Fri, 2006-04-28 at 11:29 +0200, Mike Galbraith wrote:
> On Fri, 2006-04-28 at 16:56 +0900, MAEDA Naoaki wrote:
> > On Fri, 28 Apr 2006 09:41:09 +0200
> > Mike Galbraith <efault@gmx.de> wrote:
> >
> > > On Fri, 2006-04-28 at 16:26 +0900, MAEDA Naoaki wrote:
> > > > On Fri, 28 Apr 2006 08:59:49 +0200
> > > > Mike Galbraith <efault@gmx.de> wrote:
> > > > > You simply cannot ignore interactive tasks. At the very least, you have
> > > > > to disallow requeue if the resource limit has been exceeded, otherwise,
> > > > > this patch set is non-functional.
> > > >
> > > > It can be easily implemented on top of the current code. Do you know a good
> > > > sample program that is judged as interactive but consumes lots of cpu?
> > >
> > > X sometimes, Mozilla sometimes,... KDE konsole when scrolling,...
> > > anything that on average sleeps more than roughly 5% of it's slice can
> > > starve you to death either alone, or (worse) with peers.
> >
> > They are true interactive tasks, aren't they?
> > Oh! I should say "that is not interactive, but judged as interactive
> > and consumes lots of cpu".
>
> Why do you care? There is only one thing that matters, and that is the
> fact that cpu can be used and remain utterly uncontrolled. This renders
> your system non-functional for resource management. Period. All stop.
Here's an example: this is a snippet of me doing a modest parallel
kernel compile in an nfs mounted localhost directory. What part of this
is truly interactive, and what part do you think should be excluded from
resource management?
14467 mikeg 16 0 17052 13m 3712 R 20.7 1.3 0:00.33 cc1
14498 mikeg 16 0 17052 13m 3708 S 19.7 1.3 0:00.35 cc1
14523 mikeg 16 0 14852 11m 3532 D 13.1 1.1 0:00.26 cc1
14445 mikeg 16 0 14716 11m 3692 S 12.2 1.2 0:00.25 cc1
14492 mikeg 16 0 15912 11m 3096 R 8.5 1.2 0:00.21 cc1
14469 mikeg 15 0 14892 10m 1988 D 7.5 1.0 0:00.19 cc1
14513 mikeg 25 0 11480 6508 1976 R 3.8 0.6 0:00.10 cc1
14579 mikeg 25 0 9128 4260 1908 R 3.8 0.4 0:00.04 cc1
14532 mikeg 15 0 0 0 0 Z 1.9 0.0 0:00.02 as
next prev parent reply other threads:[~2006-04-28 10:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 1:37 [PATCH 0/9] CPU controller MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 1/9] CPU controller - Add class load estimation support MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 2/9] CPU controller - Add class hungry detection support MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 3/9] CPU controller - Add timeslice scaling support MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 4/9] CPU controller - Add interface functions MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 5/9] CPU controller - Documentation how the controller works MAEDA Naoaki
2006-04-28 1:38 ` [PATCH 6/9] CPU controller - Add basic functions and registering the controller MAEDA Naoaki
2006-04-28 1:38 ` [PATCH 7/9] CPU controller - Add routines to change share values and show stat MAEDA Naoaki
2006-04-28 1:38 ` [PATCH 8/9] CPU controller - Add cpu hotplug support MAEDA Naoaki
2006-04-28 1:38 ` [PATCH 9/9] CPU controller - Documentation how to use the controller MAEDA Naoaki
2006-04-28 5:25 ` [PATCH 0/9] CPU controller Mike Galbraith
2006-04-28 5:48 ` MAEDA Naoaki
2006-04-28 6:59 ` Mike Galbraith
2006-04-28 7:26 ` MAEDA Naoaki
2006-04-28 7:41 ` Mike Galbraith
2006-04-28 7:56 ` [ckrm-tech] " MAEDA Naoaki
2006-04-28 9:29 ` Mike Galbraith
2006-04-28 10:01 ` Mike Galbraith [this message]
2006-04-28 10:11 ` Con Kolivas
2006-04-28 12:07 ` MAEDA Naoaki
2006-04-28 13:09 ` Con Kolivas
2006-04-28 13:55 ` Hirokazu Takahashi
2006-04-28 14:55 ` Con Kolivas
2006-04-28 15:39 ` Mike Galbraith
2006-04-28 5:56 ` Kirill Korotaev
2006-04-28 7:11 ` Mike Galbraith
2006-04-28 7:46 ` Mike Galbraith
2006-04-28 8:13 ` Kirill Korotaev
2006-04-28 9:35 ` Mike Galbraith
2006-04-28 10:09 ` Con Kolivas
2006-04-28 10:16 ` Mike Galbraith
2006-04-28 10:26 ` Con Kolivas
2006-04-28 10:42 ` Mike Galbraith
2006-04-28 8:28 ` MAEDA Naoaki
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=1146218469.8067.25.camel@homer \
--to=efault@gmx.de \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maeda.naoaki@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.