Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754082AbcJDIg6 (ORCPT ); Tue, 4 Oct 2016 04:36:58 -0400 Received: from resqmta-ch2-12v.sys.comcast.net ([69.252.207.44]:36908 "EHLO resqmta-ch2-12v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752585AbcJDIg4 (ORCPT ); Tue, 4 Oct 2016 04:36:56 -0400 Date: Tue, 4 Oct 2016 03:36:53 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@east.gentwo.org To: Piotr Kwapulinski cc: mtk.manpages@gmail.com, 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, 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, akpm@linux-foundation.org, linux-doc@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA memory policy documentation In-Reply-To: <20160927131948.11974-1-kwapulinski.piotr@gmail.com> Message-ID: References: <20160927131948.11974-1-kwapulinski.piotr@gmail.com> Content-Type: text/plain; charset=US-ASCII X-CMAE-Envelope: MS4wfKPuXdNqHWeASV8P/69yCBED0JY8K7zVVdrkUTM/CainM93cj3p4fuWJZ6Png92YesRft+Z28DWlVYxs9miQxQQelFkeSjAD72cI8dkaqhfmZJnOWTdX b48WLw/dGG6/X97xRO2ukQV9/bh5dE06lkAlG8TjwAeW/s5FJiDtbAhcsAG34S5eERV6KkoHt3jX/aqRGR0gCS/ZmN+WIhkafEMG6fpBRBx0i38RaPKzHEX/ G3w3kUx9jsdZjJhVkVjo4G6F0u4P3GkYCRxI/7F0uDQM358UJyXYEoKeteen0RqSK+F5u6tqkKrCX45UEQQFEmPuQGf3iF+CIVkAB9ZdL7EeJSxSM23nfG6V Ss0x6NNokn5C/PY+8yrD0xC6cDqG1yTsApIOjg4BKT97zBTMwhJ5p3NCOJedH3r2dYQvvhnS8904lrHjD335xMFKTL0Cp9C61RY4iL1gEpW5H6wqJOryvdGx nGqGTOJ9HbzktuXe79/CYLnk2zet4uz373edoVdooUcMaD476a+ROLMveYX3S8WK8t57tTMcLrCDXc2RbPyLq3HTm+/33d/5lFgm5uuOVI699mvPe7xfbn3v GfbRFZJShkKWcSt3l+kTcYYsgS5nuI8RxqIOemqfCqXe309KwU8n0QHLcoE2kfPR5XMb32eZbzXvq6uTD1K9D7pBAaR2NF35L8FcW/d5QbrgzeDEPVNUpuNe yUMxtSBeMouAPFfmgTXK1f6mmohr7kjPv8GvqxqIccsb5pf3JTeJ8XwUcNqtubH8DUY/T5xbv6H4JVr2AMuJ/2GESXgydlCvARDXsogGg4DEWI46uKvwTNHV 1/d+FKl5PPLFbP90jr/K8Tk3P0lJTT8LEQVLwepecYXWEPmK2y0LcEwXC9+18YRgLYU9pKHN+XKtBHBY7Q4= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 496 Lines: 9 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.