From: Simon Derr <Simon.Derr@bull.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lse-tech] CPUSET Proposal
Date: Fri, 26 Sep 2003 07:36:47 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106456185901844@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106442121824485@msgid-missing>
On Thu, 25 Sep 2003, Shailabh Nagar wrote:
> Coming to memory, it wasn't very clear what CPUSETs future
> plans/objectives are. Does it intend to control which address ranges a
> CPUSET can allocate from (for NUMA reasons) AND limit how much memory it
> can consume ? The latter intersects with CKRM objectives, the former
> doesn't.
The future plans are still to be decided. The control on memory provided
by future versions of CPUSET might be to:
-associate one node on wich to allocate memory to each cpuset
-associate one allocation policy (local node first, round robin) to each
cpuset.
At first glance, limiting the amount of memory used will probably not be
in our objectives. The initial goal of CPUSET was obtaining good
performance on NUMA architectures. But this is an open question.
> Finally, CKRM is dealing with I/O and planning to incorporate inbound
> and possibly outbound networking into its framework which would appear
> to be outside the scope of something like CPUSETs.
That's right.
Simon.
next prev parent reply other threads:[~2003-09-26 7:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 16:30 [Lse-tech] CPUSET Proposal Stephen Hemminger
2003-09-24 17:02 ` David Mosberger
2003-09-24 19:32 ` Gerrit Huizenga
2003-09-24 21:42 ` Paul Jackson
2003-09-25 5:40 ` Paul Jackson
2003-09-25 5:44 ` Paul Jackson
2003-09-25 6:02 ` William Lee Irwin III
2003-09-25 6:57 ` David Mosberger
2003-09-25 7:07 ` David Mosberger
2003-09-25 7:08 ` William Lee Irwin III
2003-09-25 7:14 ` William Lee Irwin III
2003-09-25 9:04 ` Dave Hansen
2003-09-25 18:07 ` Shailabh Nagar
2003-09-25 18:08 ` William Lee Irwin III
2003-09-25 20:50 ` Shailabh Nagar
2003-09-26 7:36 ` Simon Derr [this message]
2003-09-26 9:58 ` Paul Jackson
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-106456185901844@msgid-missing \
--to=simon.derr@bull.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox