[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36901495-1891-7e08-b978-955af02f3d57@intel.com>
Date: Thu, 11 Apr 2019 07:28:02 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Yang Shi <yang.shi@...ux.alibaba.com>, mhocko@...e.com,
mgorman@...hsingularity.net, riel@...riel.com, hannes@...xchg.org,
akpm@...ux-foundation.org, keith.busch@...el.com,
dan.j.williams@...el.com, fengguang.wu@...el.com, fan.du@...el.com,
ying.huang@...el.com, ziy@...dia.com
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [v2 RFC PATCH 0/9] Another Approach to Use PMEM as NUMA Node
This isn't so much another aproach, as it it some tweaks on top of
what's there. Right?
This set seems to present a bunch of ideas, like "promote if accessed
twice". Seems like a good idea, but I'm a lot more interested in seeing
data about it being a good idea. What workloads is it good for? Bad for?
These look like fun to play with, but I'd be really curious what you
think needs to be done before we start merging these ideas.
Powered by blists - more mailing lists