From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, penberg@cs.helsinki.fi, kiran@scalex86.org,
ak@suse.de
Subject: Re: [RFC] Slab: Enforce clean node lists per zone, add policy support and fallback
Date: Tue, 8 Aug 2006 11:16:52 -0700 [thread overview]
Message-ID: <20060808111652.571f85db.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608080951240.27620@schroedinger.engr.sgi.com>
Christoph wrote:
> Currently the allocations may be redirected via cpusets to other nodes.
Minor picky point of terminology ... I wouldn't say that cpusets
"redirect" the allocation, but "force" or "constrain" it. To my way
of speaking, a "redirect" would apply if the rule was "allocations
on node 6 should be satisfied on (redirected to) node 9", for
example. A forced constraint applies if the rule is "I don't care
what you asked for buddy - you're getting node 9, period."
Separate point - I think we already have a workaround in place for
the migration case to keep cpuset constraints out of the way. See
the overwriting of tsk->mems_allowed in the kernel/cpuset.c routine
cpuset_migrate_mm(). With Christoph's new __GFP_THISNODE, or whatever
alloc_pages_exact_node() with limited zonelist equivalent we come up
with, we don't need both that and the cpuset_migrate_mm() workaround.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
--
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>
next prev parent reply other threads:[~2006-08-08 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 16:56 [RFC] Slab: Enforce clean node lists per zone, add policy support and fallback Christoph Lameter
2006-08-08 18:16 ` Paul Jackson [this message]
2006-08-08 18:32 ` Christoph Lameter
2006-08-08 19:20 ` Paul Jackson
2006-08-08 18:29 ` 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=20060808111652.571f85db.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=kiran@scalex86.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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.