[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1610040333050.10814@east.gentwo.org>
Date: Tue, 4 Oct 2016 03:36:53 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: Piotr Kwapulinski <kwapulinski.piotr@...il.com>
cc: mtk.manpages@...il.com, kirill.shutemov@...ux.intel.com,
vbabka@...e.cz, rientjes@...gle.com, mhocko@...nel.org,
mgorman@...hsingularity.net, liangchen.linux@...il.com,
nzimmer@....com, a.p.zijlstra@...llo.nl, riel@...hat.com,
lee.schermerhorn@...com, jmarchan@...hat.com, joe@...ches.com,
corbet@....net, iamyooon@...il.com, n-horiguchi@...jp.nec.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-man@...r.kernel.org, akpm@...ux-foundation.org,
linux-doc@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA
memory policy documentation
Well the difference between MPOL_DEFAULT and MPOL_LOCAL may be confusing.
Mention somewhere in the MPOL_LOCAL description that the policy with
MPOL_DEFAULT reverts to the policy of the process and MPOL_LOCAL to try to
allocate local? Note that MPOL_LOCAL also will not be local if it just
happens that the local node is overallocated. This is usually confusing
for newcomers. The node/zone reclaim must be activated in order to allow
node local reclaim that results in a node local allocation.
Powered by blists - more mailing lists