nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCHv3 1/2] libnvdimm: Use max contiguous area for namespace size
Date: Fri, 20 Jul 2018 15:48:39 -0600	[thread overview]
Message-ID: <20180720214838.GB4864@localhost.localdomain> (raw)
In-Reply-To: <1532119565.10343.15.camel@intel.com>

On Fri, Jul 20, 2018 at 01:46:06PM -0700, Verma, Vishal L wrote:
> $ cat /sys/bus/nd/devices/region1/max_available_extent
> 17045651456
> 
> $ ndctl list -BNR --region=region1
> [
>   {
>     "provider":"ACPI.NFIT",
>     "dev":"ndbus1",
>     "regions":[
>       {
>         "dev":"region1",
>         "size":17045651456,
>         "available_size":0,
>         "type":"pmem",
>         "numa_node":0,
>         "persistence_domain":"unknown",
>         "namespaces":[
>           {
>             "dev":"namespace1.0",
>             "mode":"raw",
>             "size":17045651456,
>             "sector_size":512,
>             "blockdev":"pmem1",
>             "numa_node":0
>           }
> 	...
> 

As we saw, getting the "available_size" directly from the the region's
sysfs entry also returned  the same as max extent:

 $ cat /sys/bus/nd/devices/region1/available_size
 17045651456

The reason ndctl shows available_size as '0' is because the nstype is
neither of type PMEM nor BLK.

So I think max_available_extent is doing the right thing.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  parent reply	other threads:[~2018-07-20 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 15:47 [PATCHv3 1/2] libnvdimm: Use max contiguous area for namespace size Keith Busch
2018-07-12 15:47 ` [PATCHv3 2/2] libnvdimm: Export max available extent Keith Busch
2018-07-20 20:46 ` [PATCHv3 1/2] libnvdimm: Use max contiguous area for namespace size Verma, Vishal L
2018-07-20 20:54   ` Keith Busch
2018-07-20 21:48   ` Keith Busch [this message]
2018-07-20 23:17     ` 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=20180720214838.GB4864@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=stable@vger.kernel.org \
    --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).