From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 37DA521C943C4 for ; Thu, 29 Jun 2017 18:26:42 -0700 (PDT) Received: by mail-yb0-x231.google.com with SMTP id 84so34061566ybe.0 for ; Thu, 29 Jun 2017 18:28:15 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <595589CF.5010605@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> <59556E37.80808@hpe.com> <595580A6.9000004@hpe.com> <595589CF.5010605@hpe.com> From: Dan Williams Date: Thu, 29 Jun 2017 18:28:14 -0700 Message-ID: Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile ranges List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Linda Knippers Cc: Jan Kara , Matthew Wilcox , X86 ML , "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" , Al Viro , linux-fsdevel , Christoph Hellwig List-ID: On Thu, Jun 29, 2017 at 4:14 PM, Linda Knippers wrote: > 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. > A "pmem" man page sounds like a great idea, I wasn't aware we even had an sd man page. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751994AbdF3B2R (ORCPT ); Thu, 29 Jun 2017 21:28:17 -0400 Received: from mail-yb0-f169.google.com ([209.85.213.169]:35576 "EHLO mail-yb0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751333AbdF3B2P (ORCPT ); Thu, 29 Jun 2017 21:28:15 -0400 MIME-Version: 1.0 In-Reply-To: <595589CF.5010605@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> <59556E37.80808@hpe.com> <595580A6.9000004@hpe.com> <595589CF.5010605@hpe.com> From: Dan Williams Date: Thu, 29 Jun 2017 18:28:14 -0700 Message-ID: Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile ranges To: Linda Knippers Cc: "linux-nvdimm@lists.01.org" , Jan Kara , Matthew Wilcox , X86 ML , "linux-kernel@vger.kernel.org" , Al Viro , linux-fsdevel , Christoph Hellwig Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 29, 2017 at 4:14 PM, Linda Knippers wrote: > 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. > A "pmem" man page sounds like a great idea, I wasn't aware we even had an sd man page.