linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Kwapulinski <kwapulinski.piotr@gmail.com>
To: akpm@linux-foundation.org
Cc: kirill.shutemov@linux.intel.com, vbabka@suse.cz,
	rientjes@google.com, mhocko@kernel.org,
	mgorman@techsingularity.net, liangchen.linux@gmail.com,
	nzimmer@sgi.com, a.p.zijlstra@chello.nl, cl@linux.com,
	riel@redhat.com, lee.schermerhorn@hp.com, jmarchan@redhat.com,
	joe@perches.com, corbet@lwn.net, iamyooon@gmail.com,
	n-horiguchi@ah.jp.nec.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
	mtk.manpages@gmail.com, linux-doc@vger.kernel.org,
	linux-api@vger.kernel.org, kwapulinski.piotr@gmail.com
Subject: [PATCH 1/1] mm/mempolicy.c: add MPOL_LOCAL NUMA memory policy documentation
Date: Tue, 27 Sep 2016 15:22:54 +0200	[thread overview]
Message-ID: <20160927132254.12050-1-kwapulinski.piotr@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1609201304450.134671@chino.kir.corp.google.com>

The MPOL_LOCAL mode has been implemented by
Peter Zijlstra <a.p.zijlstra@chello.nl>
(commit: 479e2802d09f1e18a97262c4c6f8f17ae5884bd8).
Add the documentation for this mode.

Signed-off-by: Piotr Kwapulinski <kwapulinski.piotr@gmail.com>
---
 Documentation/vm/numa_memory_policy.txt | 8 ++++++++
 mm/mempolicy.c                          | 4 ++++
 2 files changed, 12 insertions(+)

diff --git a/Documentation/vm/numa_memory_policy.txt b/Documentation/vm/numa_memory_policy.txt
index 622b927..dcb490e 100644
--- a/Documentation/vm/numa_memory_policy.txt
+++ b/Documentation/vm/numa_memory_policy.txt
@@ -212,6 +212,14 @@ Components of Memory Policies
 	    the temporary interleaved system default policy works in this
 	    mode.
 
+	MPOL_LOCAL: This mode specifies "local allocation". It must be
+	used along with an empty nodemask. It acts like the MPOL_PREFERRED
+	mode specified with an empty nodemask. For details refer to
+	the MPOL_PREFERRED mode described above.
+
+	    Internally, it is transformed into MPOL_PREFERRED mode with an
+	    empty nodemask.
+
    Linux memory policy supports the following optional mode flags:
 
 	MPOL_F_STATIC_NODES:  This flag specifies that the nodemask passed by
diff --git a/mm/mempolicy.c b/mm/mempolicy.c
index 2da72a5..02dc43e 100644
--- a/mm/mempolicy.c
+++ b/mm/mempolicy.c
@@ -35,6 +35,10 @@
  *                use the process policy. This is what Linux always did
  *		  in a NUMA aware kernel and still does by, ahem, default.
  *
+ * local          "Local allocation". It acts like a special case of
+ *                "preferred" memory policy: NUMA_NO_NODE (see above
+ *                for details).
+ *
  * The process policy is applied for most non interrupt memory allocations
  * in that process' context. Interrupts ignore the policies and always
  * try to allocate on the local CPU. The VMA policy is only applied for memory
-- 
2.10.0

--
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>

  parent reply	other threads:[~2016-09-27 13:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18 11:29 [PATCH] mm/mempolicy.c: forbid static or relative flags for local NUMA mode Piotr Kwapulinski
2016-09-19 11:52 ` Michal Hocko
2016-09-20 15:47   ` Piotr Kwapulinski
2016-09-20  0:57 ` David Rientjes
2016-09-20 15:56   ` Piotr Kwapulinski
2016-09-20 20:05     ` David Rientjes
2016-09-27 13:19       ` [PATCH 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA memory policy documentation Piotr Kwapulinski
2016-10-04  8:36         ` Christoph Lameter
2016-10-09 18:56           ` [PATCH v2 " Piotr Kwapulinski
2016-10-10 13:55             ` Christoph Lameter
2016-10-10 16:23               ` [PATCH v3 " Piotr Kwapulinski
2016-10-12  7:55                 ` Michael Kerrisk (man-pages)
2016-10-12 14:08                   ` Christoph Lameter
2016-10-12 14:35                     ` Michael Kerrisk (man-pages)
2016-10-12 15:53                   ` Piotr Kwapulinski
2016-10-12 19:55                     ` Christoph Lameter
2016-10-13  6:48                       ` Michael Kerrisk (man-pages)
2016-09-27 13:22       ` Piotr Kwapulinski [this message]
2016-09-27 13:25       ` [PATCH v2 0/1] mm/mempolicy.c: forbid static or relative flags for local NUMA mode Piotr Kwapulinski
2016-10-27 16:30         ` [PATCH v3 " Piotr Kwapulinski
2016-11-01  0:21           ` David Rientjes
2016-09-27 13:27       ` [PATCH 1/1] man/set_mempolicy.2,mbind.2: " Piotr Kwapulinski
2016-09-20 15:12 ` [PATCH] mm/mempolicy.c: " Vlastimil Babka
2016-09-20 16:23   ` Piotr Kwapulinski

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=20160927132254.12050-1-kwapulinski.piotr@gmail.com \
    --to=kwapulinski.piotr@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=corbet@lwn.net \
    --cc=iamyooon@gmail.com \
    --cc=jmarchan@redhat.com \
    --cc=joe@perches.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=liangchen.linux@gmail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=nzimmer@sgi.com \
    --cc=riel@redhat.com \
    --cc=rientjes@google.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