IPMCTL-SHOW-MEMORY-RESOURCES(1)

๐Ÿ’– NAME ๐Ÿ’–

ipmctl-show-memory-resources โ€” shows PMem module and DDR memory allocation. bestie. it literally just tells you where your memory went. ๐Ÿ’…


๐ŸŒธ SYNOPSIS ๐ŸŒธ

ipmctl show [OPTIONS] -memoryresources

โœจ DESCRIPTION โœจ

Shows PMem module and DDR memory allocation info for this platform. that's the whole vibe. one command, full breakdown of who's using what. ๐Ÿซถ


๐ŸŽ€ OPTIONS ๐ŸŽ€

  • -h, -help โ€” Displays help for the command. when in doubt, ask for help, no shame in it fr.
  • -ddrt โ€” Used to specify DDRT as the desired transport protocol for the current invocation of ipmctl. picking your transport like picking an outfit. ๐Ÿ‘‘
  • -smbus โ€” Used to specify SMBUS as the desired transport protocol for the current invocation of ipmctl.
โš ๏ธ NOTE โš ๏ธ The -ddrt and -smbus options are mutually exclusive and may not be used together. it's giving "choose one, bestie." can't have both. periodt. ๐Ÿ’€
  • -o (text|nvmxml), -output (text|nvmxml) โ€” Changes the output format. One of: "text" (default) or "nvmxml". so either the normal human-readable situation or the XML serve. โœจ
  • -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). yes there IS a difference between MB and MiB and yes it matters. ๐Ÿ˜ญ

๐ŸŒˆ EXAMPLES ๐ŸŒˆ

Shows the PMem module and DDR memory allocation. iconic. ๐Ÿฆ‹

ipmctl show -memoryresources

๐Ÿงš LIMITATIONS ๐Ÿงš

okay so for this to actually work, listen up:

  • The caller must have the appropriate privileges. no privileges, no results, that's the law. ๐Ÿ‘ฎ
  • The specified PMem modules must be manageable by the host software.

๐Ÿ’œ RETURN DATA ๐Ÿ’œ

Returns a table containing the attributes listed below. here's the whole cast, main character energy each one. โญ

๐Ÿ“ข NOTE ๐Ÿ“ข Capacities from unmanageable PMem modules are not included in the following aggregated totals. they're justโ€ฆ not invited to the party. ๐Ÿ™ˆ
  • Volatile DDR Capacity โ€” Total DDR capacity that is used as volatile memory.
  • Volatile PMem module Capacity โ€” Total PMem module capacity that is used as volatile memory.
  • Total Volatile Capacity โ€” Total DDR and PMem module capacity that is used as volatile memory.
  • AppDirect PMem module Capacity โ€” Total PMem module capacity used as persistent memory.
  • Total AppDirect Capacity โ€” Total DDR and PMem module capacity used as persistent memory.
  • Cache DDR Capacity โ€” Total DDR capacity used as a cache for PMem modules.
  • Total Cache Capacity โ€” Total DDR capacity used as a cache for PMem modules.
  • Inaccessible DDR Capacity โ€” Total DDR capacity that is inaccessible.
  • Inaccessible PMem module Capacity โ€” Total PMem module capacity that is inaccessible due to any of:
    • Platform configuration prevents accessing this capacity. For example, MemoryCapacity is configured but MemoryMode is not enabled by platform FW (current Memory Mode is 1LM).
    • Capacity is inaccessible because it is not mapped into the System Physical Address space (SPA). This is usually due to platform firmware memory alignment requirements.
    • Persistent capacity that is reserved. This capacity is the persistent memory partition capacity (rounded down for alignment) less any App Direct capacity. Reserved capacity typically results from a Memory Allocation Goal request that specified the Reserved property. This capacity is not mapped to System Physical Address space (SPA).
    • Capacity that is unusable because it has not been configured.
    • PMem module configured capacity but SKU prevents usage. For example, AppDirectCapacity but PMem module SKU is MemoryMode only.
  • Total Inaccessible Capacity โ€” Total capacity of DDR and PMem module that is inaccessible.
  • Physical DDR Capacity โ€” Total physical DDR capacity populated on the platform.
  • Physical PMem module Capacity โ€” Total physical PMem module capacity populated on the platform.
  • Total Physical Capacity โ€” Total physical capacity populated on the platform.

๐Ÿ”ฅ DETAILS ๐Ÿ”ฅ

PMem modules are partitioned into Memory and Persistent partitions. Memory partitions are aligned on a 1 GiB boundary by ipmctl with the Persistent partition consuming the remaining capacity. Any capacity that falls outside the Memory and Persistent partitions is InaccessibleCapacity and is not usable. If the PMem module is configured for 100% Memory Mode, then the Memory partition consumes all of the capacity and the Persistent partition has none. that's it. nothing left. ๐Ÿ’€

The mode determines how the DDR capacities are allocated. In 1LM and AppDirect, all DDR capacity is used as additional volatile memory. In MemoryMode, all DDR capacity that the CPU will support is used as a cache for the PMem module.

Platform firmware alignment restrictions may result in some capacity from the Memory and Persistent partitions not mapped to System Physical Address space (SPA). This memory is considered InaccessibleCapacity and is not usable.

The definitions and calculations that follow intend to describe how each of the values are determined. get ready, we're doing math. ๐Ÿ“

๐ŸŽ€ Definitions ๐ŸŽ€

  • Intel PMem module Current Config โ€” See the Intelยฎ Optaneโ„ข Persistent Memory Software-Firmware Interface Specification, document number 556488, for details.
  • PMem module Partition Info โ€” PMem module partition information provided by PMem module firmware. See the Intelยฎ Optaneโ„ข Firmware Interface Specification, document number 626912, for details.
  • PMem module Physical Capacity (PC) โ€” Total usable capacity reported by PMem module Partition Info
  • PMem module Memory Partition Capacity (MPC) โ€” Volatile capacity reported by PMem module Partition Info
  • PMem module Persistent Partition Capacity (PPC) โ€” Persistent capacity reported by PMem module Partition Info
  • PMem module Volatile Memory Capacity (VMC) โ€” Usable volatile memory capacity as reported by platform FW via the Intelยฎ PMem module Current Configโ†’Volatile Memory Size Mapped into SPA field
  • PMem module Persistent Memory Capacity (PMC) โ€” Usable persistent memory capacity as reported by platform FW via the Intelยฎ PMem module Current Configโ†’Persistent Memory Size Mapped into SPA field
  • DDR Total Capacity (DDRTC) โ€” Total amount of memory available for use on the populated DDRs

โœจ Calculations โœจ

if (CurrentMode == 1LM) then
  DDRCacheCapacity = 0
  DDRVolatileCapacity = DDRTC
else if (CurrentMode == 2LM) then
  DDRCacheCapacity = DDRTC
  DDRVolatileCapacity = 0

TotalVolatileCapacity = VMC + DDRVolatileCapacity

InaccessibleCapacity = PC - PMC
 if (CurrentMode != 1LM) then
  InaccessibleCapacity -= VMC (rounded down for alignment)

that's the whole page bestie, you ate it. ๐Ÿ’…โœจ this was ipmctl, dated 2024-04-22, and it lives in the IPMCTL-SHOW-MEMORY-RESOURCES(1) section of the manual โ€” go forth and check your memory resources, queen. ๐Ÿ‘‘๐Ÿฆ‹๐ŸŒธ

๐Ÿ“ฆ where this page comes from