Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1328721303095 for ; Thu, 8 Aug 2019 08:28:02 -0700 (PDT) From: Jeff Moyer Subject: Re: [ndctl PATCH] Documentation/namespace-description: Clarify label-less restrictions References: <20190807221815.25782-1-vishal.l.verma@intel.com> Date: Thu, 08 Aug 2019 11:25:30 -0400 In-Reply-To: <20190807221815.25782-1-vishal.l.verma@intel.com> (Vishal Verma's message of "Wed, 7 Aug 2019 16:18:15 -0600") Message-ID: MIME-Version: 1.0 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: Vishal Verma Cc: linux-nvdimm@lists.01.org List-ID: Vishal Verma writes: > In the ndctl-create-namespace (and related) man pages, add a > clarification note regarding some of the restrictions a user may see > when operating on label-less namespaces. > > Link: https://github.com/pmem/ndctl/issues/52 > Reported-by: Jane Chu > Cc: Dan Williams > Signed-off-by: Vishal Verma > --- > Documentation/ndctl/namespace-description.txt | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/ndctl/namespace-description.txt b/Documentation/ndctl/namespace-description.txt > index 94999e5..5f294be 100644 > --- a/Documentation/ndctl/namespace-description.txt > +++ b/Documentation/ndctl/namespace-description.txt > @@ -18,6 +18,12 @@ the kernel's 'memmap=ss!nn' command line option (see the nvdimm wiki on > kernel.org), or NVDIMMs without a valid 'namespace index' in their label > area. > > +NOTE: Label-less namespaces lack many of the features of their label-rich > +cousins. For example, their size cannot be modified, or they cannot be > +'destroyed' (only disabled). The only operation supported on them is to > +change their 'mode', by adding on-media metadata which is then used to > +identify an address abstraction mechanism for the namespace. That last sentence is way too obtuse. You could end it at the word 'mode'. -Jeff _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm