From: Peter Williams <pwil3058@bigpond.net.au>
To: Mike Galbraith <efault@gmx.de>
Cc: balbir@in.ibm.com, Martin Ohlin <martin.ohlin@control.lth.se>,
linux-kernel@vger.kernel.org
Subject: Re: A nice CPU resource controller
Date: Thu, 31 Aug 2006 15:21:02 +1000 [thread overview]
Message-ID: <44F671BE.6000607@bigpond.net.au> (raw)
In-Reply-To: <1157007190.6035.14.camel@Homer.simpson.net>
Mike Galbraith wrote:
> On Thu, 2006-08-31 at 11:07 +1000, Peter Williams wrote:
>
>> But your implication here is valid. It is better to fiddle with the
>> dynamic priorities than with nice as this leaves nice for its primary
>> purpose of enabling the sysadmin to effect the allocation of CPU
>> resources based on external considerations.
>
> I don't understand. It _is_ the administrator fiddling with nice based
> on external considerations. It just steadies the administrator's hand.
Not exactly. If "nice" is being (automatically) fiddled to meet some
measurable requirement such as the amount of CPU tasks get it is no
longer available as a means for the indication of the relative
importance of the tasks. I.e. it can't be both the means for saying
which tasks should be allocated the most CPU and the means by which that
allocation is controlled.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2006-08-31 5:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 15:14 A nice CPU resource controller Martin Ohlin
2006-08-30 15:41 ` Balbir Singh
2006-08-30 16:13 ` Martin Ohlin
2006-08-31 6:03 ` Balbir Singh
2006-08-31 1:07 ` Peter Williams
2006-08-31 6:17 ` Balbir Singh
2006-08-31 10:08 ` Peter Williams
2006-08-31 10:44 ` Mike Galbraith
2006-08-31 6:53 ` Mike Galbraith
2006-08-31 5:21 ` Peter Williams [this message]
2006-08-31 7:44 ` Mike Galbraith
2006-08-31 7:42 ` Mike Galbraith
2006-08-31 10:35 ` Martin Ohlin
2006-08-31 14:17 ` Mike Galbraith
2006-08-31 16:01 ` Chris Friesen
2006-08-31 19:14 ` Mike Galbraith
2006-08-31 23:52 ` Peter Williams
2006-08-31 10:21 ` Martin Ohlin
2006-08-31 11:13 ` Balbir Singh
2006-08-31 18:25 ` Peter Grandi
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=44F671BE.6000607@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=balbir@in.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.ohlin@control.lth.se \
/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