From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "Scargall, Steve" <steve.scargall@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH 3/3] ndctl/namespace: add a --continue option to create namespaces greedily
Date: Thu, 29 Aug 2019 18:05:01 +0000 [thread overview]
Message-ID: <44b020035e3245084b2310cfdfe496853e2cf18d.camel@intel.com> (raw)
In-Reply-To: <CAPcyv4gB-2hkPM=zKCigpDAUxQbzWFVRmZ=UnTF0wsBW3-nmsQ@mail.gmail.com>
On Wed, 2019-08-28 at 19:34 -0700, Dan Williams wrote:
> On Wed, Aug 28, 2019 at 5:17 PM Vishal Verma <vishal.l.verma@intel.com> wrote:
> > Add a --continue option to ndctl-create-namespaces to allow the creation
> > of as many namespaces as possible, that meet the given filter
> > restrictions.
> >
> > The creation loop will be aborted if a failure is encountered at any
> > point.
> >
> > Link: https://github.com/pmem/ndctl/issues/106
> > Reported-by: Steve Scargal <steve.scargall@intel.com>
> > Cc: Jeff Moyer <jmoyer@redhat.com>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> > ---
> > .../ndctl/ndctl-create-namespace.txt | 7 ++++++
> > ndctl/namespace.c | 25 +++++++++++++++----
> > 2 files changed, 27 insertions(+), 5 deletions(-)
> >
> > diff --git a/Documentation/ndctl/ndctl-create-namespace.txt b/Documentation/ndctl/ndctl-create-namespace.txt
> > index c9ae27c..55a8581 100644
> > --- a/Documentation/ndctl/ndctl-create-namespace.txt
> > +++ b/Documentation/ndctl/ndctl-create-namespace.txt
> > @@ -215,6 +215,13 @@ include::xable-region-options.txt[]
> > --bus=::
> > include::xable-bus-options.txt[]
> >
> > +-c::
> > +--continue::
> > + Do not stop after creating one namespace. Instead, greedily create as
>
> I like the "greedy" terminology here because it makes the option seem
> a bit off-putting. "Do you really want to be greedy?"
Ha, I just borrowed it from regular expressions :)
>
> > + many namespaces as possible within the given --bus and --region filter
> > + restrictions. This will abort if any creation attempt results in an
> > + error.
>
> Hmm, should "--continue --force" override that policy?
Yep that's a good idea, with a big note in the man page that errors
could be lost/meaningless in that case.
>
> Otherwise this looks good to me.
Thanks, I'll send a new version with the above.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2019-08-29 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 0:17 [ndctl PATCH 0/3] greedy namespace creation Vishal Verma
2019-08-29 0:17 ` [ndctl PATCH 1/3] Documentation: refactor 'bus options' into its own include Vishal Verma
2019-08-29 0:17 ` [ndctl PATCH 2/3] Documentation: clarify bus/dimm/region filtering Vishal Verma
2019-08-29 0:17 ` [ndctl PATCH 3/3] ndctl/namespace: add a --continue option to create namespaces greedily Vishal Verma
2019-08-29 2:34 ` Dan Williams
2019-08-29 18:05 ` Verma, Vishal L [this message]
2019-08-29 19:08 ` Vishal Verma
2019-08-29 17:38 ` jane.chu
2019-08-29 18:08 ` Verma, Vishal L
2019-08-29 18:28 ` Dan Williams
2019-08-29 19:16 ` jane.chu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44b020035e3245084b2310cfdfe496853e2cf18d.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=steve.scargall@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).