From: Mike Galbraith <efault@gmx.de>
To: balbir@in.ibm.com
Cc: Peter Williams <pwil3058@bigpond.net.au>,
Martin Ohlin <martin.ohlin@control.lth.se>,
linux-kernel@vger.kernel.org
Subject: Re: A nice CPU resource controller
Date: Thu, 31 Aug 2006 10:44:40 +0000 [thread overview]
Message-ID: <1157021080.5770.88.camel@Homer.simpson.net> (raw)
In-Reply-To: <44F67EE2.5060605@in.ibm.com>
On Thu, 2006-08-31 at 11:47 +0530, Balbir Singh wrote:
> It's my belief that time and priorities are orthogonal. Nice does a good job
> of trying to mix the two, but in the case of resource management it might not
> be such a good idea.
I don't think they're orthogonal. If two tasks of identical priority
are contending for cpu, and you choose the one with more time on it's
group ticket, you have effectively modified priorities.
Regardless, nice sounded attractive to me at first, but it's flat wrong
to use a per task variable to store group scope information, so I have
to agree that nice isn't a good choice for group resource management.
-Mike
next prev parent reply other threads:[~2006-08-31 8:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 15:14 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 [this message]
2006-08-31 6:53 ` Mike Galbraith
2006-08-31 5:21 ` Peter Williams
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=1157021080.5770.88.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.ohlin@control.lth.se \
--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
Powered by JetHome