From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Piotr Kwapulinski <kwapulinski.piotr@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
David Rientjes <rientjes@google.com>,
mhocko@kernel.org, mgorman@techsingularity.net,
Liang Chen <liangchen.linux@gmail.com>,
nzimmer@sgi.com, Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
jmarchan@redhat.com, Joe Perches <joe@perches.com>,
Jonathan Corbet <corbet@lwn.net>,
SeokHoon Yoon <iamyooon@gmail.com>,
n-horiguchi@ah.jp.nec.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-man <linux-man@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-doc@vger.kernel.org, Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH v3 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA memory policy documentation
Date: Wed, 12 Oct 2016 16:35:26 +0200 [thread overview]
Message-ID: <CAKgNAkjLLLkyU1-H_ur802o=mNnpOC0XAb_3TPRSc-RuRNYZFg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1610120906150.14274@east.gentwo.org>
Hi Christoph,
On 12 October 2016 at 16:08, Christoph Lameter <cl@linux.com> wrote:
> On Wed, 12 Oct 2016, Michael Kerrisk (man-pages) wrote:
>
>> > +arguments must specify the empty set. If the "local node" is low
>> > +on free memory the kernel will try to allocate memory from other
>> > +nodes. The kernel will allocate memory from the "local node"
>> > +whenever memory for this node is available. If the "local node"
>> > +is not allowed by the process's current cpuset context the kernel
>> > +will try to allocate memory from other nodes. The kernel will
>> > +allocate memory from the "local node" whenever it becomes allowed
>> > +by the process's current cpuset context. In contrast
>> > +.B MPOL_DEFAULT
>> > +reverts to the policy of the process which may have been set with
>> > +.BR set_mempolicy (2).
>> > +It may not be the "local allocation".
>>
>> What is the sense of "may not be" here? (And repeated below).
>> Is the meaning "this could be something other than"?
>> Presumably the answer is yes, in which case I'll clarify
>> the wording there. Let me know.
>
> Someone may have set for example a round robin policy with numactl
> --interleave before starting the process? Then allocations will go through
> all nodes.
So the sense is then "this could be something other than", right?
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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:[~2016-10-12 14:35 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) [this message]
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 ` [PATCH 1/1] mm/mempolicy.c: " Piotr Kwapulinski
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='CAKgNAkjLLLkyU1-H_ur802o=mNnpOC0XAb_3TPRSc-RuRNYZFg@mail.gmail.com' \
--to=mtk.manpages@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=kwapulinski.piotr@gmail.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=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