public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Martin Ohlin <martin.ohlin@control.lth.se>
Cc: Mike Galbraith <efault@gmx.de>,
	Peter Williams <pwil3058@bigpond.net.au>,
	balbir@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: A nice CPU resource controller
Date: Thu, 31 Aug 2006 10:01:57 -0600	[thread overview]
Message-ID: <44F707F5.4090008@nortel.com> (raw)
In-Reply-To: <44F6BB8A.7090001@control.lth.se>

Martin Ohlin wrote:

> Maybe I am wrong, but as I see it, if one wants to control on a group 
> level, then the individual shares within the group are not that 
> important. If the individual share is important, then it should be 
> controlled on a per-task level. Please tell me if I am wrong.

The individual share within the group may not be important, but the 
relative priority might be.


We have instances were we would like to express something like:

--these tasks are all grouped together as "maintenance" tasks, and 
should be guaranteed 3% of the system together
	--within the maintenance tasks, my network heartbeat application is the 
most latency sensitive, so I want it to be higher-priority than the 
other maintenance tasks


 From my point of view, task group cpu allocation and relative task 
priority should be orthogonal.

First you pick a task group (based on cpu share, priority, etc.) then 
within the group you pick the task with highest priority.

This was something that CKRM did right (IMHO).

Chris

  parent reply	other threads:[~2006-08-31 16:02 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
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 [this message]
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=44F707F5.4090008@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=balbir@in.ibm.com \
    --cc=efault@gmx.de \
    --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