From: Hubertus Franke <frankeh@watson.ibm.com>
To: Peter Williams <peterw@aurema.com>
Cc: Rik van Riel <riel@redhat.com>,
Shailabh Nagar <nagar@watson.ibm.com>,
kanderso@redhat.com, Chandra Seetharaman <sekharan@us.ibm.com>,
limin@sgi.com, jlan@sgi.com, linux-kernel@vger.kernel.org,
jh@sgi.com, Paul Jackson <pj@sgi.com>,
gh@us.ibm.com, Erik Jacobson <erikj@subway.americas.sgi.com>,
ralf@suse.de, lse-tech@lists.sourceforge.net,
Vivek Kashyap <kashyapv@us.ibm.com>,
mason@suse.com
Subject: Re: [Lse-tech] Re: Minutes from 5/19 CKRM/PAGG discussion
Date: Tue, 25 May 2004 11:13:12 -0400 [thread overview]
Message-ID: <40B36288.9050205@watson.ibm.com> (raw)
In-Reply-To: <40B2A78E.3060302@aurema.com>
Peter Williams wrote:
> Hubertus Franke wrote:
>
>>
>> One important input the PAGG team could give is some real
>> examples where actually multiple associations to different groups
>> is required and help us appreciate that position and let us
>> see how this would/could be done in CKRM.
>
>
> One example would be the implementation of CPU sets (or pools) a la
> Solaris where there are named CPU pools to which processors and
> processes are assigned. Processors can be moved between CPU pools
> and when this happens it is necessary to visit all the processes that
> are assigned to the pools involved (one losing and one gaining the
> processor) and change their CPU affinity masks to reflect the new
> assignment of processors. PAGG would be ideal for implementing this.
>
> At the same time, a resource management client could be controlling
> resources allocated to processes based on some other criteria such as
> the real user or the application being run without regard to which CPU
> pool they are running in.
>
> Peter
Good one, at question though is again though is whether the very
communalities warrant some realignment. We want to hook into the base
schedulers and be the clearing house or umbrella to consolidate all the
ideas, such as the well defined RCFS recently introduced together with
Rik van Riel. PAGG is as stated a way of doing things outside the core
kernel and hookable schedulers have been several times rejected at the
lkml base.
One potential is to agree that the communalities are so few that it
makes sense to continue with both approaches independently.
-- Hubertus
next prev parent reply other threads:[~2004-05-25 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 17:09 Minutes from 5/19 CKRM/PAGG discussion Hanna Linder
2004-05-24 17:39 ` Hanna Linder
2004-05-24 18:05 ` Rik van Riel
2004-05-24 19:55 ` Hubertus Franke
2004-05-24 23:43 ` Peter Williams
2004-05-25 15:00 ` Hubertus Franke
2004-05-26 1:31 ` Peter Williams
2004-05-25 1:55 ` Peter Williams
2004-05-25 4:26 ` Peter Williams
2004-05-25 15:19 ` Hubertus Franke
2004-05-26 1:53 ` Peter Williams
2004-05-25 15:13 ` Hubertus Franke [this message]
2004-05-26 1:44 ` [Lse-tech] " Peter Williams
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=40B36288.9050205@watson.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=erikj@subway.americas.sgi.com \
--cc=gh@us.ibm.com \
--cc=jh@sgi.com \
--cc=jlan@sgi.com \
--cc=kanderso@redhat.com \
--cc=kashyapv@us.ibm.com \
--cc=limin@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mason@suse.com \
--cc=nagar@watson.ibm.com \
--cc=peterw@aurema.com \
--cc=pj@sgi.com \
--cc=ralf@suse.de \
--cc=riel@redhat.com \
--cc=sekharan@us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox