Dell PowerEdge MX750c EMC PMem 200 Series Users Guide - Page 35

Figure 17. Memory Devices in Device Manager PMem Disk management Windows currently supports only one namespace per interleave set (this is independent of the number of physical devices in the interleave set). The option to interleave PMems can be selected during goal creation as described in App Direct and Memory mode configurations. PMem disks have to be created with the help of "New-Pmemdisk" command by providing relevant region IDs. Once PMem disks are configured, PMem volumes can be used as normal disks. Windows supports the following PowerShell cmdlets to manage persistent memory: ● Get-PmemDisk ○ Returns one or more logical persistent memory disks. ○ The returned object has information about size, atomicity type, health status, and underlying physical devices. ● Get-PmemPhysicalDevice ○ Returns one or more physical persistent memory devices (NVDIMMs). ○ The returned object has information about size, RFIC, device location, and health/operational status. ● New-PmemDisk ○ Creates a new disk out of a given unused region. ○ Writes out the labels to create the namespace then rebuilds the SCM stacks to expose the new logical device. ○ Optional parameters: ￭ FriendlyName gives the persistent memory disk a friendly name. Default is "PmemDisk". ￭ AtomicityType lets you set BTT. Default is "none." ● Remove-PmemDisk ○ Removes the given persistent memory disk. It accepts the output of Get-PmemDisk. ○ Deletes the namespace's labels and then rebuilds the SCM stacks to remove the logical device. ○ Requires user confirmation, which can be overridden with Force. ● Get-PmemUnusedRegion ○ Returns aggregate PMem regions available for provisioning a logical device. ○ Returned object has a unique region ID, total size, and list of physical devices that contribute to the unused region. ● Initialize-PmemPhysicalDevice ○ Writes zeroes to the label storage area, writes new label index blocks, and then rebuilds the SCM stacks to reflect the changes. Windows 35