From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile ranges To: Dan Williams 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> <59556E37.80808@hpe.com> <595580A6.9000004@hpe.com> CC: "linux-nvdimm@lists.01.org" , Jan Kara , Matthew Wilcox , X86 ML , "linux-kernel@vger.kernel.org" , Al Viro , linux-fsdevel , Christoph Hellwig From: Linda Knippers Message-ID: <595589CF.5010605@hpe.com> Date: Thu, 29 Jun 2017 19:14:23 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 06/29/2017 06:58 PM, Dan Williams wrote: > On Thu, Jun 29, 2017 at 3:49 PM, Linda Knippers 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. -- ljk