From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f70.google.com (mail-oi0-f70.google.com [209.85.218.70]) by kanga.kvack.org (Postfix) with ESMTP id 43E0D6B0005 for ; Mon, 7 May 2018 15:29:57 -0400 (EDT) Received: by mail-oi0-f70.google.com with SMTP id x134-v6so17092771oif.19 for ; Mon, 07 May 2018 12:29:57 -0700 (PDT) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id p82-v6sor10647869oih.250.2018.05.07.12.29.56 for (Google Transport Security); Mon, 07 May 2018 12:29:56 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1525704627-30114-1-git-send-email-yehs1@lenovo.com> <20180507184622.GB12361@bombadil.infradead.org> From: Dan Williams Date: Mon, 7 May 2018 12:29:55 -0700 Message-ID: Subject: Re: [RFC PATCH v1 0/6] use mm to manage NVDIMM (pmem) zone Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Jeff Moyer Cc: Matthew Wilcox , Michal Hocko , Huaisheng Ye , linux-nvdimm , Tetsuo Handa , chengnt@lenovo.com, Dave Hansen , Linux Kernel Mailing List , pasha.tatashin@oracle.com, Linux MM , colyli@suse.de, Johannes Weiner , Andrew Morton , Sasha Levin , Mel Gorman , Vlastimil Babka On Mon, May 7, 2018 at 12:28 PM, Jeff Moyer wrote: > Dan Williams 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.