Lines Matching refs:PMEM
17 LIBNVDIMM PMEM
18 PMEM-REGIONs, Atomic Sectors, and DAX
49 PMEM:
51 block device composed of PMEM is capable of DAX. A PMEM address range
63 mmap persistent memory, from a PMEM block device, directly into a
78 table with atomic update semantics to front a PMEM block device
83 (persistently names) capacity allocated to different PMEM namespaces. It
86 layered on top of a PMEM namespace, or an address abstraction like BTT
93 The LIBNVDIMM subsystem provides support for PMEM described by platform
124 LIBNVDIMM PMEM
131 specification standardizes not only the description of PMEM, but also
134 PMEM (nd_pmem.ko): Drives a system-physical-address range. This range is
142 the PMEM range. In contrast ND_NAMESPACE_IO ranges, once registered,
146 PMEM-REGIONs, Atomic Sectors, and DAX
150 update guarantees it can register a BTT on a PMEM device or partition. See
177 socket. Each PMEM interleave set is identified by a region device with
181 single PMEM namespace is created in the REGION0-SPA-range that spans most
184 another PMEM namespace to be defined.
188 well as DIMM2 and DIMM3. Some of REGION1 is allocated to a PMEM namespace
383 A generic REGION device is registered for each PMEM interleave-set /
384 range. Per the example there are 2 PMEM regions on the "nfit_test.0"
466 represents DIMM-info-backed PMEM (note that it has a 'uuid' attribute), and
467 namespace1.0 represents an anonymous PMEM namespace (note that has no 'uuid'