[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3cee267e-6a5b-a5a3-698b-4261bef13543@intel.com>
Date: Tue, 9 Mar 2021 13:53:13 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Yang Shi <shy828301@...il.com>,
Dave Hansen <dave.hansen@...ux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux MM <linux-mm@...ck.org>,
Yang Shi <yang.shi@...ux.alibaba.com>,
David Rientjes <rientjes@...gle.com>,
Huang Ying <ying.huang@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
David Hildenbrand <david@...hat.com>,
Oscar Salvador <osalvador@...e.de>
Subject: Re: [PATCH 10/10] mm/migrate: new zone_reclaim_mode to enable reclaim
migration
On 3/8/21 4:24 PM, Yang Shi wrote:
>> Once this is enabled page demotion may move data to a NUMA node
>> that does not fall into the cpuset of the allocating process.
>> This could be construed to violate the guarantees of cpusets.
>> However, since this is an opt-in mechanism, the assumption is
>> that anyone enabling it is content to relax the guarantees.
> I think we'd better have the cpuset violation paragraph along with new
> zone reclaim mode text so that the users are aware of the potential
> violation. I don't think commit log is the to-go place for any plain
> users.
>
Agreed. I'll add it to the Documentation/.
Powered by blists - more mailing lists