From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"ross.zwisler@linux.intel.com" <ross.zwisler@linux.intel.com>,
"Busch, Keith" <keith.busch@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"Jiang, Dave" <dave.jiang@intel.com>
Cc: "y-goto@jp.fujitsu.com" <y-goto@jp.fujitsu.com>
Subject: Re: [PATCH] ndctl: Use max_available_extent for creating namespaces
Date: Tue, 26 Jun 2018 16:19:28 +0000 [thread overview]
Message-ID: <1530029963.27147.21.camel@intel.com> (raw)
In-Reply-To: <20180626153736.6770-3-keith.busch@intel.com>
On Tue, 2018-06-26 at 09:37 -0600, Keith Busch wrote:
> The available_size attribute returns all the unused regions, but a
> namespace has to use contiguous free regions. This patch uses the
> attribute returning the largest capacity that can be created for
> determining if the namespace can be created.
>
> Signed-off-by: Keith Busch <keith.busch@intel.com>
> ---
> ndctl/lib/libndctl.c | 30 ++++++++++++++++++++++++++++++
> ndctl/lib/libndctl.sym | 1 +
> ndctl/libndctl.h | 2 ++
> ndctl/namespace.c | 2 +-
> 4 files changed, 34 insertions(+), 1 deletion(-)
Hi Keith,
The patch looks good, but just a couple of 'meta' comments.
1. We typically send ndctl patches separately from kernel patches (i.e. not
thraded together).
2. for ndctl patches, an 'ndctl PATCH' prefix is recommended. You can set a
repo local config parameter for doing this automatically on git format-
patch.
git config format.subjectprefix "ndctl PATCH"
I'm thinking the kernel changes will be queued for 4.19, which means the
ndctl changes will go into v62.
Thanks,
-Vishal
>
> diff --git a/ndctl/lib/libndctl.c b/ndctl/lib/libndctl.c
> index 47e005e..a820fb3 100644
> --- a/ndctl/lib/libndctl.c
> +++ b/ndctl/lib/libndctl.c
> @@ -2025,6 +2025,36 @@ NDCTL_EXPORT unsigned long long
> ndctl_region_get_available_size(
> return strtoull(buf, NULL, 0);
> }
>
> +NDCTL_EXPORT unsigned long long ndctl_region_get_max_available_extent(
> + struct ndctl_region *region)
> +{
> + unsigned int nstype = ndctl_region_get_nstype(region);
> + struct ndctl_ctx *ctx = ndctl_region_get_ctx(region);
> + char *path = region->region_buf;
> + int len = region->buf_len;
> + char buf[SYSFS_ATTR_SIZE];
> +
> + switch (nstype) {
> + case ND_DEVICE_NAMESPACE_PMEM:
> + case ND_DEVICE_NAMESPACE_BLK:
> + break;
> + default:
> + return 0;
> + }
> +
> + if (snprintf(path, len,
> + "%s/max_available_extent", region->region_path) >=
> len) {
> + err(ctx, "%s: buffer too small!\n",
> + ndctl_region_get_devname(region));
> + return ULLONG_MAX;
> + }
> +
> + if (sysfs_read_attr(ctx, path, buf) < 0)
> + return ULLONG_MAX;
> +
> + return strtoull(buf, NULL, 0);
> +}
> +
> NDCTL_EXPORT unsigned int ndctl_region_get_range_index(struct
> ndctl_region *region)
> {
> return region->range_index;
> diff --git a/ndctl/lib/libndctl.sym b/ndctl/lib/libndctl.sym
> index c1228e5..22fd026 100644
> --- a/ndctl/lib/libndctl.sym
> +++ b/ndctl/lib/libndctl.sym
> @@ -123,6 +123,7 @@ global:
> ndctl_region_get_mappings;
> ndctl_region_get_size;
> ndctl_region_get_available_size;
> + ndctl_region_get_max_available_extent;
> ndctl_region_get_type;
> ndctl_region_get_namespace_seed;
> ndctl_region_get_btt_seed;
> diff --git a/ndctl/libndctl.h b/ndctl/libndctl.h
> index be997ac..624115d 100644
> --- a/ndctl/libndctl.h
> +++ b/ndctl/libndctl.h
> @@ -338,6 +338,8 @@ unsigned int ndctl_region_get_interleave_ways(struct
> ndctl_region *region);
> unsigned int ndctl_region_get_mappings(struct ndctl_region *region);
> unsigned long long ndctl_region_get_size(struct ndctl_region *region);
> unsigned long long ndctl_region_get_available_size(struct ndctl_region
> *region);
> +unsigned long long ndctl_region_get_max_available_extent(
> + struct ndctl_region *region);
> unsigned int ndctl_region_get_range_index(struct ndctl_region *region);
> unsigned int ndctl_region_get_type(struct ndctl_region *region);
> struct ndctl_namespace *ndctl_region_get_namespace_seed(
> diff --git a/ndctl/namespace.c b/ndctl/namespace.c
> index fe86d82..4a562a2 100644
> --- a/ndctl/namespace.c
> +++ b/ndctl/namespace.c
> @@ -764,7 +764,7 @@ static int namespace_create(struct ndctl_region
> *region)
> return -EAGAIN;
> }
>
> - available = ndctl_region_get_available_size(region);
> + available = ndctl_region_get_max_available_extent(region);
> if (!available || p.size > available) {
> debug("%s: insufficient capacity size: %llx avail:
> %llx\n",
> devname, p.size, available);
_______________________________________________
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-26 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 15:37 [PATCH 0/2] Namespace creation fixups Keith Busch
2018-06-26 15:37 ` [PATCH 1/2] libnvdimm: Use largest contiguous area for namespace size Keith Busch
2018-07-05 17:57 ` Dan Williams
2018-07-05 17:58 ` Keith Busch
2018-06-26 15:37 ` [PATCH] ndctl: Use max_available_extent for creating namespaces Keith Busch
2018-06-26 16:19 ` Verma, Vishal L [this message]
2018-06-26 16:29 ` Keith Busch
2018-06-26 16:27 ` Verma, Vishal L
2018-06-26 16:32 ` Dan Williams
2018-06-26 16:34 ` Verma, Vishal L
2018-06-26 15:37 ` [PATCH 2/2] libnvdimm: Export max available extent Keith Busch
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=1530029963.27147.21.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=y-goto@jp.fujitsu.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).