[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4gbnqv4=mKPyiDskGKE9HveN6S9rzSmYGQ7QjCPg6W0cQ@mail.gmail.com>
Date: Mon, 7 May 2018 12:29:55 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Jeff Moyer <jmoyer@...hat.com>
Cc: Matthew Wilcox <willy@...radead.org>,
Michal Hocko <mhocko@...e.com>,
Huaisheng Ye <yehs1@...ovo.com>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
chengnt@...ovo.com, Dave Hansen <dave.hansen@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
pasha.tatashin@...cle.com, Linux MM <linux-mm@...ck.org>,
colyli@...e.de, Johannes Weiner <hannes@...xchg.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Sasha Levin <alexander.levin@...izon.com>,
Mel Gorman <mgorman@...hsingularity.net>,
Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [RFC PATCH v1 0/6] use mm to manage NVDIMM (pmem) zone
On Mon, May 7, 2018 at 12:28 PM, Jeff Moyer <jmoyer@...hat.com> wrote:
> Dan Williams <dan.j.williams@...el.com> writes:
[..]
>>> What's the use case?
>>
>> Use NVDIMMs as System-RAM given their potentially higher capacity than
>> DDR. The expectation in that case is that data is forfeit (not
>> persisted) after a crash. Any persistent use case would need to go
>> through the pmem driver, filesystem-dax or device-dax.
>
> OK, but that sounds different from what was being proposed, here. I'll
> quote from above:
>
>>>>>> But for the critical pages, which we hope them could be recovered
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>> from power fail or system crash, we make them to be persistent by
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>> storing them to NVM zone.
>
> Hence my confusion.
Yes, now mine too, I overlooked that.
Powered by blists - more mailing lists