Lines Matching refs:namespace
38 libnvdimm: namespace
39 libndctl: namespace enumeration example
40 libndctl: namespace creation example
41 Why the Term "namespace"?
221 BLK-namespace can be configured with a BTT with unique atomic sector
223 not provide for a sector size to be specified for a PMEM namespace.
259 single PMEM namespace is created in the REGION0-SPA-range that spans most
269 well as DIMM2 and DIMM3. Some of REGION1 is allocated to a PMEM namespace
486 "nstype" indicates the integer type of namespace-device this region
577 1. There are already more than two REGION and "namespace" types. For
598 named "namespace". This generic format of the device-model hierarchy
616 The whole point of region/namespace device type differentiation is to
617 decide which block-device driver will attach to a given LIBNVDIMM namespace.
667 surfaces one or more "namespace" devices. The arrival of a "namespace"
671 LIBNVDIMM: namespace
676 attribute), namespace2.0 represents a BLK namespace (note it has a
678 PMEM namespace (note that has no 'uuid' attribute due to not support a
721 LIBNDCTL: namespace enumeration example
725 no guarantees in this regard. For a static namespace identifier use its
742 LIBNDCTL: namespace creation example
746 region has enough available capacity to create a new namespace.
747 Namespace instantiation involves finding an idle namespace and
748 configuring it. For the most part the setting of namespace attributes
759 snprintf(devname, sizeof(devname), "namespace%d.%d",
773 Why the Term "namespace"?
797 seed device. To activate it set the "namespace", "uuid", and
802 |-- namespace
818 finding and idle BTT and assigning it to consume a PMEM or BLK namespace::
849 Once a "namespace" is removed from a BTT that instance of the BTT device
855 can be suppressed by enabling raw mode for the namespace via the