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 12:20:29 -0700 [thread overview]
Message-ID: <20060808122029.01e91c2a.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608081129410.28922@schroedinger.engr.sgi.com>
> You are confusing two issues in the migration code. The case of
> sys_migrate_page was fixed by you by changing the cpuset context. Thats
> fine and we do not need __GFP_THISNODE there because the page are to be
> allocated in conformity with a cpuset context of a process.
Ah - ok. Yes, I was looking for the constraints of the new, destination
cpuset, rather than the tasks curent cpuset. And I was not looking for
exact __GFP_THISNODE placement. So I was talking about a separate case.
Minor confusion with a confusion ... I don't know why you mentioned
'sys_migrate_page' -- that wasn't what I was referring to. I was
referring to my cpuset_migrate_mm() hack, which is involved in the two
cases:
1) a task is put in a cpuset that is marked 'memory_migrate', or
2) a task is in a cpuset marked 'memory_migrate' and that cpusets
'mems' are changed.
In any case ... nevermind ;).
--
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 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 16:56 Christoph Lameter
2006-08-08 18:16 ` Paul Jackson
2006-08-08 18:32 ` Christoph Lameter
2006-08-08 19:20 ` Paul Jackson [this message]
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=20060808122029.01e91c2a.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox