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.
