From: Christoph Lameter <clameter@sgi.com>
To: Michael Kerrisk <michael.kerrisk@gmx.net>
Cc: Andrew Morton <akpm@osdl.org>,
clameter@sgi.comclameter@sgi.com, ak@suse.de, linux-mm@kvack.org,
mtk-manpages@gmx.net
Subject: Re: Inconsistent capabilites associated with MPOL_MOVE_ALL
Date: Tue, 14 Mar 2006 17:16:04 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0603141715340.23371@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <441820B0.6719.396D781@michael.kerrisk.gmx.net>
On Wed, 15 Mar 2006, Michael Kerrisk wrote:
> Ooops sorry about the last -- I see that Christoph is changing stuff in
> addition to what I was proposing... (But it makes sense to me, from a
> consistency point of view.)
No these are all related to MPOL_MOVE_ALL. Either for mbind() or
migrate_pages().
--
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-03-15 1:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 16:58 numa_maps update Christoph Lameter
2006-03-04 9:07 ` Andrew Morton
2006-03-04 4:59 ` Andi Kleen
2006-03-04 20:08 ` Christoph Lameter
2006-03-04 20:26 ` Andrew Morton
2006-03-06 16:19 ` Christoph Lameter
2006-03-06 17:37 ` Christoph Lameter
2006-03-15 0:01 ` Inconsistent capabilites associated with MPOL_MOVE_ALL Michael Kerrisk
2006-03-15 0:09 ` Christoph Lameter
2006-03-15 0:25 ` Michael Kerrisk
2006-03-15 0:33 ` Christoph Lameter
2006-03-15 0:40 ` Michael Kerrisk
2006-03-15 0:41 ` Andrew Morton
2006-03-15 0:53 ` Christoph Lameter
2006-03-15 1:01 ` Andrew Morton
2006-03-15 1:07 ` Michael Kerrisk
2006-03-15 1:12 ` Michael Kerrisk
2006-03-15 1:16 ` Christoph Lameter [this message]
2006-03-15 1:08 ` Christoph Lameter
2006-03-15 0:59 ` Michael Kerrisk
2006-03-15 1:16 ` Andrew Morton
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=Pine.LNX.4.64.0603141715340.23371@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.comclameter \
--cc=michael.kerrisk@gmx.net \
/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