From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, pj@sgi.com
Subject: Re: [RFC] mbind: Restrict nodes to the currently allowed cpuset
Date: Wed, 10 Jan 2007 01:23:56 +0100 [thread overview]
Message-ID: <200701100123.56852.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0701041115220.22710@schroedinger.engr.sgi.com>
On Thursday 04 January 2007 20:16, Christoph Lameter wrote:
> Currently one can specify an arbitrary node mask to mbind that includes nodes
> not allowed. If that is done with an interleave policy then we will go around
> all the nodes. Those outside of the currently allowed cpuset will be redirected
> to the border nodes. Interleave will then create imbalances at the borders
> of the cpuset.
>
> This patch restricts the nodes to the currently allowed cpuset.
Fine by me.
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-01-10 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 19:16 Christoph Lameter
2007-01-04 19:20 ` Paul Jackson
2007-01-10 0:23 ` Andi Kleen [this message]
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=200701100123.56852.ak@suse.de \
--to=ak@suse.de \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.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