From: Dan Williams <dan.j.williams@intel.com>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: Yigal Korman <yigal.korman@netapp.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH v2] ndctl, list: display the 'map' location in listings
Date: Fri, 1 Jun 2018 17:01:52 -0700 [thread overview]
Message-ID: <CAPcyv4gs7fNLLXx96neHWVVdn_A74_SeDWRKT4054jX5U_21YQ@mail.gmail.com> (raw)
In-Reply-To: <20180529231503.31710-1-vishal.l.verma@intel.com>
On Tue, May 29, 2018 at 4:15 PM, Vishal Verma <vishal.l.verma@intel.com> wrote:
> For 'fsdax' and 'devdax' namespaces, a 'map' location may be specified
> for page structures storage. This can be 'mem', for system RAM, or 'dev'
> for using pmem as the backing storage. Once set, there was no way of
> telling using ndctl, which of the two locations a namespace was
> configured for. Add this in util_namespace_to_json so that all
> namespace listings contain the map location.
>
> Reported-by: "Yigal Korman" <yigal.korman@netapp.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> ---
> util/json.c | 32 +++++++++++++++++++++++++++-----
> 1 file changed, 27 insertions(+), 5 deletions(-)
>
> v2: Also account for memmap=ss!nn or legacy-e820 namespaces. (Dan)
>
> diff --git a/util/json.c b/util/json.c
> index c606e1c..b020300 100644
> --- a/util/json.c
> +++ b/util/json.c
> @@ -667,11 +667,17 @@ struct json_object *util_namespace_to_json(struct ndctl_namespace *ndns,
> {
> struct json_object *jndns = json_object_new_object();
> struct json_object *jobj, *jbbs = NULL;
> + const char *locations[] = {
> + [NDCTL_PFN_LOC_NONE] = "none",
> + [NDCTL_PFN_LOC_RAM] = "mem",
> + [NDCTL_PFN_LOC_PMEM] = "dev",
> + };
> unsigned long long size = ULLONG_MAX;
> unsigned int sector_size = UINT_MAX;
> enum ndctl_namespace_mode mode;
> const char *bdev = NULL, *name;
> unsigned int bb_count = 0;
> + enum ndctl_pfn_loc loc;
we could initialize loc to NDCTL_PFN_LOC_NONE here.
> struct ndctl_btt *btt;
> struct ndctl_pfn *pfn;
> struct ndctl_dax *dax;
> @@ -693,33 +699,49 @@ struct json_object *util_namespace_to_json(struct ndctl_namespace *ndns,
> mode = ndctl_namespace_get_mode(ndns);
> switch (mode) {
> case NDCTL_NS_MODE_MEMORY:
> - if (pfn) /* dynamic memory mode */
> + jobj = json_object_new_string("fsdax");
> + if (jobj)
> + json_object_object_add(jndns, "mode", jobj);
> + loc = ndctl_pfn_get_location(pfn);
NULL ptr de-reference if pfn is NULL
> + if (pfn) { /* dynamic memory mode */
> size = ndctl_pfn_get_size(pfn);
> - else /* native/static memory mode */
> + jobj = json_object_new_string(locations[loc]);
> + } else { /* native/static memory mode */
> size = ndctl_namespace_get_size(ndns);
> - jobj = json_object_new_string("fsdax");
> + jobj = json_object_new_string("mem");
We could just set NDCTL_PFN_LOC_RAM here.
> + }
> + if (jobj)
> + json_object_object_add(jndns, "map", jobj);
> break;
> case NDCTL_NS_MODE_DAX:
> if (!dax)
> goto err;
> size = ndctl_dax_get_size(dax);
> jobj = json_object_new_string("devdax");
> + if (jobj)
> + json_object_object_add(jndns, "mode", jobj);
> + loc = ndctl_dax_get_location(dax);
> + jobj = json_object_new_string(locations[loc]);
> + if (jobj)
> + json_object_object_add(jndns, "map", jobj);
> break;
> case NDCTL_NS_MODE_SAFE:
> if (!btt)
> goto err;
> jobj = json_object_new_string("sector");
> + if (jobj)
> + json_object_object_add(jndns, "mode", jobj);
> size = ndctl_btt_get_size(btt);
> break;
> case NDCTL_NS_MODE_RAW:
> size = ndctl_namespace_get_size(ndns);
> jobj = json_object_new_string("raw");
> + if (jobj)
> + json_object_object_add(jndns, "mode", jobj);
> break;
> default:
> jobj = NULL;
> }
> - if (jobj)
> - json_object_object_add(jndns, "mode", jobj);
Why is mode getting moved into each case?
I'd put the
jobj = json_object_new_string(locations[loc]);
if (jobj)
json_object_object_add(jndns, "map", jobj);
...at the end here and just gate it on mode != NDCTL_NS_MODE_SAFE &&
mode != NDCTL_NS_MODE_RAW
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-06-02 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 23:15 [ndctl PATCH v2] ndctl, list: display the 'map' location in listings Vishal Verma
2018-06-02 0:01 ` Dan Williams [this message]
2018-06-04 23:21 ` Verma, Vishal L
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=CAPcyv4gs7fNLLXx96neHWVVdn_A74_SeDWRKT4054jX5U_21YQ@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=vishal.l.verma@intel.com \
--cc=yigal.korman@netapp.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).