MAN page from Fedora 30 ipmctl-01.00.00.3474-1.fc30.x86_64.rpm
Section: ipmctl (1)
ipmctl-show-memory-resources - Shows the total DCPMM memory resource allocation
ipmctl show [OPTIONS] -memoryresources
Shows the total DCPMM memory resource allocation across the host server.
- Displays help for the command.
-o (text|nvmxml), -output (text|nvmxml)
- Changes the output format. One of: "text" (default) or "nvmxml".
-u (B|MB|MiB|GB|GiB|TB| TiB), -units (B|MB|MiB|GB|GiB|TB| TiB)
- Changes the units that capacities are displayed in for this command. One of:bytes (B), megabytes (MB), mebibytes (MiB), gigabytes (GB), gibibytes (GiB),terabytes (TB) or tebibytes (TiB).
Shows the DCPMM memory resource allocation.
ipmctl show -memoryresources
Returns the default attributes listed below.
Capacities from unmanageable DCPMMs are not included in the followingaggregated totals.
- Total system DCPMM capacity.
- Total usable system DCPMM Memory Mode capacity.
- Total usable system DCPMM App Direct capacity.
- Total system DCPMM capacity that is unusable because it has not been configured.
- Total system DCPMM persistent memory capacity that is reserved. This capacityis the persistent memory partition capacity (rounded down for alignment)less any App Direct capacity. Reserved capacity typically results froma Memory Allocation Goal request that specified the Reserved property. Thiscapacity is not mapped to system physical address (SPA) space.
- Total system DCPMM capacity that is inaccessible due any of:
- *Platform configuration prevents accessing this capacity. e.g. MemoryCapacity isconfigured but MemoryMode is not enabled by platform FW (current Memory Mode is 1LM).
- *Capacity is inaccessible because it is not mapped into the system physicaladdress space (SPA). This is usually due to platform firmware memory alignment requirements.
- *DCPMM configured capacity but SKU prevents usage. e.g. AppDirectCapcity butDCPMM SKU is MemoryMode only.
DCPMMs are partitioned into Memory and Persistent partitions. ipmctl will alignthe Memory partition on a 1 GiB boundary with the Persistent partition consumingthe remaining capacity. An exception: if DCPMM is configured for 100% Memory Modethen Memory partition will consume 100% of the capacity, while Persistentpartition will be 0 length. Any capacity that falls outside the Memory andPersistent partitions is InaccessibleCapacity and is not useable.
Platform firmware alignment restrictions may result in some capacity from theMemory and Persistent partitions not mapped to system physical address (SPA) space.This memory is considered InaccessibleCapacity and is not usable.
Total Capacity (TC)
- Raw Capacity (total usable) reported by DCPMM DIMM Partition Info
Memory Partition Capacity (MPC)
- Volatile Capacity reported by DCPMM DIMM Partition Info
Persistent Partition Capacity (PPC)
- Persistent Capacity reported by DCPMM DIMM Partition Info
Volatile Memory Size (VMS)
- Usable volatile memory capacity as reported by platform FWvia Intel NVDIMM Current Config->Volatile Memory Size Mapped into SPA field
Persistent Memory Size (PMS)
- Usable persistent memory capacity as reported by platform FW viaIntel NVDIMM Current Config->Persistent Memory Size Mapped into SPA field
DCPMM DIMM Partition Info
- DIMM Partition Info provided by DCPMM firmware. See Intel® OptanetmDC Persistent Memory Module Firmware Interface Specification for details.
Intel NVDIMM Current Config
- See Intel® NVM Dimm Management Software-Firmware Interface Specificationfor details.
MemoryCapacity = Volatile Memory Size
AppDirectCapacity = Persistent Memory Size
ReservedCapacity = PPC (rounded down for PM alignment) - PMS
InaccessibleCapacity = + (TC - MPC - PPC) + (TC - PMS - ReservedCapacity) if (CurrentMode == 1LM) then + VMS (rounded down for alignment)
- RETURN DATA
This document was created byman2html,using the manual pages.