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 11:29:12 +0200 [thread overview]
Message-ID: <1146216552.8067.11.camel@homer> (raw)
In-Reply-To: <20060428165639.0e4f9a03.maeda.naoaki@jp.fujitsu.com>
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.
-Mike
next prev parent reply other threads:[~2006-04-28 9:29 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 [this message]
2006-04-28 10:01 ` Mike Galbraith
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=1146216552.8067.11.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.