linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kravetz <mike.kravetz@oracle.com>
To: linux-man@vger.kernel.org, linux-mm@kvack.org,
	Alejandro Colomar <alx@kernel.org>
Cc: Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
	Lorenzo Stoakes <lstoakes@gmail.com>,
	Mike Kravetz <mike.kravetz@oracle.com>
Subject: [PATCH] mbind.2: Clarify MPOL_MF_MOVE with MPOL_INTERLEAVE policy
Date: Fri,  5 May 2023 12:48:58 -0700	[thread overview]
Message-ID: <20230505194858.23539-1-mike.kravetz@oracle.com> (raw)

There was user confusion about specifying MPOL_MF_MOVE* with
MPOL_INTERLEAVE policy [1].  Add clarification.

[1] https://lore.kernel.org/linux-mm/20230501185836.GA85110@monkey/

Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
---
 man2/mbind.2 | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/man2/mbind.2 b/man2/mbind.2
index d540bbe23..e4a187106 100644
--- a/man2/mbind.2
+++ b/man2/mbind.2
@@ -311,6 +311,10 @@ If
 is also specified, then the call fails with the error
 .B EIO
 if some pages could not be moved.
+If the
+.B MPOL_INTERLEAVE
+policy was specified, pages already residing on the specified
+nodes will not be moved such that they are interleaved.
 .PP
 If
 .B MPOL_MF_MOVE_ALL
@@ -326,6 +330,10 @@ If
 is also specified, then the call fails with the error
 .B EIO
 if some pages could not be moved.
+If the
+.B MPOL_INTERLEAVE
+policy was specified, pages already residing on the specified
+nodes will not be moved such that they are interleaved.
 .\" ---------------------------------------------------------------
 .SH RETURN VALUE
 On success,
-- 
2.40.0


             reply	other threads:[~2023-05-05 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 19:48 Mike Kravetz [this message]
2023-05-05 19:58 ` [PATCH] mbind.2: Clarify MPOL_MF_MOVE with MPOL_INTERLEAVE policy Alejandro Colomar
2023-05-06 18:52 ` Michal Hocko

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=20230505194858.23539-1-mike.kravetz@oracle.com \
    --to=mike.kravetz@oracle.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lstoakes@gmail.com \
    --cc=mhocko@suse.com \
    --cc=vbabka@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).