From: jane.chu@oracle.com
To: Vishal Verma <vishal.l.verma@intel.com>, linux-nvdimm@lists.01.org
Cc: Steve Scargall <steve.scargall@intel.com>
Subject: Re: [ndctl PATCH 3/3] ndctl/namespace: add a --continue option to create namespaces greedily
Date: Thu, 29 Aug 2019 10:38:40 -0700 [thread overview]
Message-ID: <179261bd-9812-6bba-6710-19a77cf3acc6@oracle.com> (raw)
In-Reply-To: <20190829001735.30289-4-vishal.l.verma@intel.com>
Hi, Vishal,
On 8/28/19 5:17 PM, Vishal Verma 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.
Just wondering what is the motivation behind providing this option?
thanks!
-jane
>
> 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
> + many namespaces as possible within the given --bus and --region filter
> + restrictions. This will abort if any creation attempt results in an
> + error.
> +
> include::../copyright.txt[]
>
> SEE ALSO
> diff --git a/ndctl/namespace.c b/ndctl/namespace.c
> index af20a42..8d6b249 100644
> --- a/ndctl/namespace.c
> +++ b/ndctl/namespace.c
> @@ -41,6 +41,7 @@ static struct parameters {
> bool do_scan;
> bool mode_default;
> bool autolabel;
> + bool greedy;
> const char *bus;
> const char *map;
> const char *type;
> @@ -114,7 +115,9 @@ OPT_STRING('t', "type", ¶m.type, "type", \
> OPT_STRING('a', "align", ¶m.align, "align", \
> "specify the namespace alignment in bytes (default: 2M)"), \
> OPT_BOOLEAN('f', "force", &force, "reconfigure namespace even if currently active"), \
> -OPT_BOOLEAN('L', "autolabel", ¶m.autolabel, "automatically initialize labels")
> +OPT_BOOLEAN('L', "autolabel", ¶m.autolabel, "automatically initialize labels"), \
> +OPT_BOOLEAN('c', "continue", ¶m.greedy, \
> + "continue creating namespaces as long as the filter criteria are met")
>
> #define CHECK_OPTIONS() \
> OPT_BOOLEAN('R', "repair", &repair, "perform metadata repairs"), \
> @@ -1365,8 +1368,11 @@ static int do_xaction_namespace(const char *namespace,
> rc = namespace_create(region);
> if (rc == -EAGAIN)
> continue;
> - if (rc == 0)
> - *processed = 1;
> + if (rc == 0) {
> + (*processed)++;
> + if (param.greedy)
> + continue;
> + }
> return rc;
> }
> ndctl_namespace_foreach_safe(region, ndns, _n) {
> @@ -1427,9 +1433,15 @@ static int do_xaction_namespace(const char *namespace,
> /*
> * Namespace creation searched through all candidate
> * regions and all of them said "nope, I don't have
> - * enough capacity", so report -ENOSPC
> + * enough capacity", so report -ENOSPC. Except during
> + * greedy namespace creation using --continue as we
> + * may have created some namespaces already, and the
> + * last one in the region search may preexist.
> */
> - rc = -ENOSPC;
> + if (param.greedy && (*processed) > 0)
> + rc = 0;
> + else
> + rc = -ENOSPC;
> }
>
> return rc;
> @@ -1487,6 +1499,9 @@ int cmd_create_namespace(int argc, const char **argv, struct ndctl_ctx *ctx)
> rc = do_xaction_namespace(NULL, ACTION_CREATE, ctx, &created);
> }
>
> + if (param.greedy)
> + fprintf(stderr, "created %d namespace%s\n", created,
> + created == 1 ? "" : "s");
> if (rc < 0 || (!namespace && created < 1)) {
> fprintf(stderr, "failed to %s namespace: %s\n", namespace
> ? "reconfigure" : "create", strerror(-rc));
>
_______________________________________________
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 17:40 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
2019-08-29 19:08 ` Vishal Verma
2019-08-29 17:38 ` jane.chu [this message]
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=179261bd-9812-6bba-6710-19a77cf3acc6@oracle.com \
--to=jane.chu@oracle.com \
--cc=linux-nvdimm@lists.01.org \
--cc=steve.scargall@intel.com \
--cc=vishal.l.verma@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).