[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43c53a7a-63cc-1968-eb5f-59115f918441@intel.com>
Date: Thu, 21 Feb 2019 15:14:55 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Adam Manzanares <Adam.Manzanares@....com>,
"lsf-pc@...ts.linux-foundation.org"
<lsf-pc@...ts.linux-foundation.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"willy@...radead.org" <willy@...radead.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"yang.shi@...ux.alibaba.com" <yang.shi@...ux.alibaba.com>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"cl@...ux.com" <cl@...ux.com>,
"jglisse@...hat.com" <jglisse@...hat.com>,
"mhocko@...e.com" <mhocko@...e.com>, "jack@...e.cz" <jack@...e.cz>
Subject: Re: [LSF/MM TOPIC] Page Cache Flexibility for NVM
On 2/21/19 3:11 PM, Adam Manzanares wrote:
> I am proposing that as an alternative to using NVMs as a NUMA node
> we expose the NVM through the page cache or a viable alternative and
> have userspace applications mmap the NVM and hand out memory with
> their favorite userspace memory allocator.
Are you proposing that the kernel manage this memory (it's managed in
the buddy lists, for instance) or that something else manage the memory,
like we do for device-dax or HMM?
Powered by blists - more mailing lists