[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190108145256.GX31793@dhcp22.suse.cz>
Date: Tue, 8 Jan 2019 15:52:56 +0100
From: Michal Hocko <mhocko@...nel.org>
To: Jonathan Cameron <jonathan.cameron@...wei.com>
Cc: Fengguang Wu <fengguang.wu@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Memory Management List <linux-mm@...ck.org>,
kvm@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Fan Du <fan.du@...el.com>, Yao Yuan <yuan.yao@...el.com>,
Peng Dong <dongx.peng@...el.com>,
Huang Ying <ying.huang@...el.com>,
Liu Jingqi <jingqi.liu@...el.com>,
Dong Eddie <eddie.dong@...el.com>,
Dave Hansen <dave.hansen@...el.com>,
Zhang Yi <yi.z.zhang@...ux.intel.com>,
Dan Williams <dan.j.williams@...el.com>,
Mel Gorman <mgorman@...e.de>,
Andrea Arcangeli <aarcange@...hat.com>,
linux-accelerators@...ts.ozlabs.org
Subject: Re: [RFC][PATCH v2 00/21] PMEM NUMA node and hotness
accounting/migration
On Wed 02-01-19 12:21:10, Jonathan Cameron wrote:
[...]
> So ideally I'd love this set to head in a direction that helps me tick off
> at least some of the above usecases and hopefully have some visibility on
> how to address the others moving forwards,
Is it sufficient to have such a memory marked as movable (aka only have
ZONE_MOVABLE)? That should rule out most of the kernel allocations and
it fits the "balance by migration" concept.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists