Lines Matching refs:namespace

32 	        libnvdimm: namespace
33 	        libndctl: namespace enumeration example
34 	        libndctl: namespace creation example
35 	        Why the Term "namespace"?
192 BLK-namespace can be configured with a BTT with unique atomic sector
194 not provide for a sector size to be specified for a PMEM namespace.
229     single PMEM namespace is created in the REGION0-SPA-range that spans most
239     well as DIMM2 and DIMM3.  Some of REGION1 is allocated to a PMEM namespace
432 "nstype" indicates the integer type of namespace-device this region
520     1. There are already more than two REGION and "namespace" types.  For
541     named "namespace".  This generic format of the device-model hierarchy
558     The whole point of region/namespace device type differentiation is to
559     decide which block-device driver will attach to a given LIBNVDIMM namespace.
606 surfaces one or more "namespace" devices.  The arrival of a "namespace"
610 LIBNVDIMM: namespace
613 attribute), namespace2.0 represents a BLK namespace (note it has a
615 PMEM namespace (note that has no 'uuid' attribute due to not support a
658 LIBNDCTL: namespace enumeration example
661 no guarantees in this regard.  For a static namespace identifier use its
676 LIBNDCTL: namespace creation example
678 region has enough available capacity to create a new namespace.
679 Namespace instantiation involves finding an idle namespace and
680 configuring it.  For the most part the setting of namespace attributes
691         snprintf(devname, sizeof(devname), "namespace%d.%d",
705 Why the Term "namespace"?
726 seed device.  To activate it set the "namespace", "uuid", and
731 	|-- namespace
745 finding and idle BTT and assigning it to consume a PMEM or BLK namespace.
776 Once a "namespace" is removed from a BTT that instance of the BTT device
782 can be suppressed by enabling raw mode for the namespace via the