From: Paul Jackson <pj@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lse-tech] Re: CPUSET Proposal
Date: Thu, 25 Sep 2003 06:38:04 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106447204008302@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106444308519469@msgid-missing>
> Well, the thing is, CKRM essentially has the cross-resource bits and
> makes up some group that can be joined and departed from and inherited
> and so on with all the right knobs ...
The hierarchies don't correspond, or do so only accidentally.
That is, cpusets, as proposed, have a hierarchy such that one
cpuset is the child of another if one cpuset describes a subset
of another's CPUs.
At first blush, I don't see a hierarchy of CKRM Classes, rather
just a flat space, say Gold, Silver and Bronze.
"When all you have is a hammer, the whole world looks like a nail"
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2003-09-25 6:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 22:26 [Lse-tech] Re: CPUSET Proposal Hanna Linder
2003-09-25 5:39 ` Paul Jackson
2003-09-25 5:48 ` William Lee Irwin III
2003-09-25 6:09 ` Paul Jackson
2003-09-25 6:23 ` William Lee Irwin III
2003-09-25 6:38 ` Paul Jackson [this message]
2003-09-25 6:44 ` William Lee Irwin III
2003-09-25 6:51 ` Paul Jackson
2003-09-25 6:59 ` William Lee Irwin III
2003-09-25 7:11 ` Paul Jackson
2003-09-25 13:11 ` Hubertus Franke
2003-09-25 13:19 ` Hubertus Franke
2003-09-25 13:21 ` Hubertus Franke
2003-09-25 13:26 ` Simon Derr
2003-09-25 16:50 ` Dave Hansen
2003-09-25 18:49 ` Luck, Tony
2003-09-25 20:28 ` Yu, Fenghua
2003-09-26 7:17 ` Sylvain Jeaugey
2003-09-26 7:47 ` Sylvain Jeaugey
2003-09-26 12:57 ` Hubertus Franke
2003-09-26 13:29 ` Hubertus Franke
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=marc-linux-ia64-106447204008302@msgid-missing \
--to=pj@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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.