From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
        "Knippers, Linda" <linda.knippers@hpe.com>
CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "hch@lst.de" <hch@lst.de>,
        "viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
        "x86@kernel.org" <x86@kernel.org>,
        "mawilcox@microsoft.com" <mawilcox@microsoft.com>,
        "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
        "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
        "jack@suse.cz" <jack@suse.cz>
Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile
 ranges
Thread-Topic: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile
 ranges
Thread-Index: AQHS8QGnKkts09hmeUykqHaORyWjLKI8N3yAgAAW54CAAAmYgIAACV8AgAAGVgCAAAR7gIAAAckAgAACPYCAAAHVAIAAAn8AgAAEW4CAACVlAIAJTuiA
Date: Wed, 5 Jul 2017 23:46:00 +0000
Message-ID: <1499297819.2042.5.camel@hpe.com>
References: <149875877608.10031.17813337234536358002.stgit@dwillia2-desk3.amr.corp.intel.com>
         <149875884190.10031.6179599135820559644.stgit@dwillia2-desk3.amr.corp.intel.com>
         <595552F5.5040008@hpe.com>
         <CAPcyv4jr0U-a521+wAL7RDca_AoUrtvO6yeY6d0UQpY7d=CHuQ@mail.gmail.com>
         <59556E37.80808@hpe.com>
         <CAPcyv4g6ijkWncZAbP-Bmbf+J7a2hR-JFLSX-ji6v-+oG0PDJQ@mail.gmail.com>
         <d073b4a1-ff90-b44a-adf2-ad44c0d70c69@hpe.com>
         <CAPcyv4huf0ENTz=LEVC6xC7xKRPc-GAZJsZMTSYpy+UoaduTMg@mail.gmail.com>
         <595580A6.9000004@hpe.com>
         <CAPcyv4gtTYEUELPtr9mi5QkGL+cm=jcFR-Oe07OCuNM9izh6jA@mail.gmail.com>
         <d545a1ea-0199-7462-58c5-067cdc22cacc@hpe.com>
         <CAPcyv4gnkpWXJ7jOJ7r0kWLKoLfuqJzdHTjANBUPztyTWUrOjA@mail.gmail.com>
         <595589CF.5010605@hpe.com>
         <CAPcyv4iTaXc92ggQcBnqJ=P0jsMF9HhnV4nAsr1Qos4pjrRDLA@mail.gmail.com>
In-Reply-To: <CAPcyv4iTaXc92ggQcBnqJ=P0jsMF9HhnV4nAsr1Qos4pjrRDLA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <1644281EC7992B45957F7A84574234DC@NAMPRD84.PROD.OUTLOOK.COM>
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jul 2017 23:46:00.5632
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DF4PR84MB0073
X-OriginatorOrg: hpe.com
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by nfs id v65NlPiB020082
Content-Length: 2103
Lines: 54

On Thu, 2017-06-29 at 18:28 -0700, Dan Williams wrote:
> On Thu, Jun 29, 2017 at 4:14 PM, Linda Knippers <linda.knippers@hpe.c
> om> wrote:
> > On 06/29/2017 06:58 PM, Dan Williams wrote:
> > > On Thu, Jun 29, 2017 at 3:49 PM, Linda Knippers <linda.knippers@h
> > > pe.com> wrote:
> > > > > The parent region of the namespace will have a 'volatile'
> > > > > type:
> > > > > 
> > > > > # cat /sys/bus/nd/devices/region0/devtype
> > > > > nd_volatile
> > > > 
> > > > 
> > > > If all I know is the /dev/pmem device name, how do I find that?
> > > > 
> > > 
> > >     cat $(readlink -f /sys/block/pmem0/device)/../devtype
> > > 
> > > ...this is where 'ndctl list' will get the information.
> > > 
> > 
> > Thanks.
> > 
> > I think we need a section 4 pmem manpage like exists for
> > mem, sd, fd, md, etc., where we can put stuff like this, as well
> > as providing some overview information that will point people to
> > other resources.  I'll give that some thought unless there is one
> > already that I'm not finding.
> > 
> 
> A "pmem" man page sounds like a great idea, I wasn't aware we even
> had an sd man page.

Sorry for being late to respond, but I agree with Linda that this 
naming policy is likely to confuse users.  I also care less about the
current users who use memmap option.  This case is pmem-emulation and
they know what they are doing.

Assuming block device interface is needed (in addition to device-dax)
for volatile range for use-cases like swap device, I wonder if user can
actually specify a right pmem device for swap from OS-install GUI when
both volatile and persistent block devices are listed as /dev/pmemN. 
Sometimes we are restricted with GUI menu.  Some users use GUI all the
time like Windows as well.

Can we differentiate the naming by adding 'v' like 'pmemNv' (if you
can't go with 'vmemN')?  I don't think having 's' for BTT was that bad.
 It's been helpful to tell users that these pmem devices are not byte-
addressable.  I also think that BTT for volatile range makes no sense
(unless emulated as persistent memory by memmap option).

Thanks,
-Toshi