From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
vatsa@in.ibm.com, Sam Vilain <sam@vilain.net>,
Kirill Korotaev <dev@openvz.org>, Mike Galbraith <efault@gmx.de>,
Ingo Molnar <mingo@elte.hu>,
Peter Williams <pwil3058@bigpond.net.au>,
Andrew Morton <akpm@osdl.org>, Balbir Singh <balbir@in.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] CPU controllers?
Date: Mon, 19 Jun 2006 12:11:25 -0700 [thread overview]
Message-ID: <1150744285.30901.6.camel@linuxchandra> (raw)
In-Reply-To: <4496E982.3040607@nortel.com>
On Mon, 2006-06-19 at 12:14 -0600, Chris Friesen wrote:
> Nick Piggin wrote:
>
> > So, from my POV, I would like to be convinced of the need for this first.
> > I would really love to be able to keep core kernel simple and fast even if
> > it means edge cases might need to use a slightly different solution.
>
> We currently use a heavily modified CKRM version "e".
>
> The "resource groups" (formerly known as CKRM) cpu controls express what
> we'd like to do, but they aren't nearly accurate enough. We don't make
> use the limits, but we do use per-cpu guarantees, along with the
> hierarchy concept.
>
> Our engineering guys need to be able to make cpu guarantees for the
> various type of processes. "main server app gets 90%, these fault
> handling guys normally get 2% but should be able to burst to 100% for up
> to 100ms, that other group gets 5% in total, but a subset of them should
> get priority over the others, and this little guy here should only be
> guaranteed .5% but it should take priority over everything else on the
> system as long as it hasn't used all its allocation".
>
> Ideally they'd really like sub percentage (.1% would be nice, but .5% is
> proably more realistic) accuracy over the divisions. This should be
> expressed per-cpu, and tasks should be migrated as necessary to maintain
> fairness. (Ie, a task belonging to a group with 50% on each cpu should
> be able to run essentially continuously, bouncing back and forth between
> cpus.) In our case, predictability/fairness comes first, then performance.
>
> If a method is accepted into mainline, it would be nice to have NPTL
> support it as a thread attribute so that different threads can be in
> different groups.
>
Chris,
Resource Groups(CKRM) does allow threads to be in different Resource
Groups ( and since Resource Group assignment is dynamic, a thread can
move to a high priority resource group for a specific operation and get
back to its original resource group after the operation is complete).
Just wondering if that is sufficient or you _would_ need support from
NPTL.
chandra
> Chris
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
next prev parent reply other threads:[~2006-06-19 19:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 13:46 [RFC] CPU controllers? Srivatsa Vaddagiri
2006-06-15 21:52 ` Sam Vilain
2006-06-15 23:30 ` Peter Williams
2006-06-16 0:42 ` Matt Helsley
2006-06-17 8:48 ` Nick Piggin
2006-06-17 15:55 ` Balbir Singh
2006-06-17 16:48 ` Srivatsa Vaddagiri
2006-06-18 5:06 ` Nick Piggin
2006-06-18 5:53 ` Sam Vilain
2006-06-18 6:11 ` Nick Piggin
2006-06-18 6:40 ` Sam Vilain
2006-06-18 7:17 ` Nick Piggin
2006-06-18 6:42 ` Andrew Morton
2006-06-18 7:28 ` Nick Piggin
2006-06-19 19:03 ` Resource Management Requirements (was "[RFC] CPU controllers?") Chandra Seetharaman
2006-06-20 5:40 ` Srivatsa Vaddagiri
2006-06-18 7:36 ` [RFC] CPU controllers? Mike Galbraith
2006-06-18 7:49 ` Nick Piggin
2006-06-18 7:49 ` Nick Piggin
2006-06-18 9:09 ` Andrew Morton
2006-06-18 9:49 ` Mike Galbraith
2006-06-19 6:28 ` Mike Galbraith
2006-06-19 6:35 ` Andrew Morton
2006-06-19 6:46 ` Mike Galbraith
2006-06-19 18:21 ` Chris Friesen
2006-06-20 6:20 ` Mike Galbraith
2006-06-18 7:18 ` Srivatsa Vaddagiri
2006-06-19 2:07 ` Sam Vilain
2006-06-19 7:04 ` MAEDA Naoaki
2006-06-19 8:19 ` Sam Vilain
2006-06-19 8:41 ` MAEDA Naoaki
2006-06-19 8:53 ` Sam Vilain
2006-06-19 21:44 ` MAEDA Naoaki
2006-06-19 18:14 ` Chris Friesen
2006-06-19 19:11 ` Chandra Seetharaman [this message]
2006-06-19 20:28 ` Chris Friesen
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=1150744285.30901.6.camel@linuxchandra \
--to=sekharan@us.ibm.com \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=cfriesen@nortel.com \
--cc=dev@openvz.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
--cc=sam@vilain.net \
--cc=vatsa@in.ibm.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.