From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Lameter Subject: Re: [PATCH RFC v2 4/4] mm/mempolicy: add nodes_empty check in SYSC_migrate_pages Date: Tue, 7 Nov 2017 09:55:47 -0600 (CST) Message-ID: References: <1509099265-30868-1-git-send-email-xieyisheng1@huawei.com> <1509099265-30868-5-git-send-email-xieyisheng1@huawei.com> <04e4cb50-8cba-58af-1a5e-61e818cffa70@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <04e4cb50-8cba-58af-1a5e-61e818cffa70@suse.cz> Sender: owner-linux-mm@kvack.org To: Vlastimil Babka Cc: Yisheng Xie , akpm@linux-foundation.org, mhocko@suse.com, mingo@kernel.org, rientjes@google.com, n-horiguchi@ah.jp.nec.com, salls@cs.ucsb.edu, linux-mm@kvack.org, linux-kernel@vger.kernel.org, tanxiaojun@huawei.com, linux-api@vger.kernel.org, Andi Kleen List-Id: linux-api@vger.kernel.org On Tue, 7 Nov 2017, Vlastimil Babka wrote: > > Migrate pages moves the pages of a single process there is no TARGET > > process. > > migrate_pages(2) takes a pid argument > > "migrate_pages() attempts to move all pages of the process pid that > are in memory nodes old_nodes to the memory nodes in new_nodes. " Ok missed that. Most use cases here are on the current process. Fundamentally a process can have shared pages outside of the cpuset that a process is restricted to. Thus I would think that migration to any of the allowed nodes of the current process that is calling migrate pages is ok. The caller wants this and the caller has a right to allocate on these nodes. It would be strange if migrate_pages would allow allocation outside of the current cpuset. > > Thus thehe *target* nodes need to be a subset of the current cpu set. And therefore the above still holds. -- 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: email@kvack.org