# Concepts

## Persistent Memory Concepts

This section describes the basic concepts when configuring and managing NVDIMMs. The following describes terms used throughout this chapter.

**Interleave Sets:** two or more NVDIMMs create an N-Way interleave set to provide striped read/write operations for increased throughput. Commonly 2-Way or 4-Way interleaving.

**Region:** a grouping of one or more NVDIMMs, or an interleaved set, that can be divided up into one or more Namespaces. Regions are created within interleaved sets.

**Label Storage Area (LSA):** Namespaces are defined by Labels which are stored in the Label Storage Area(s).

**Namespace:** defines a contiguously-addressed range of Non-Volatile Memory conceptually similar to a hard disk partition, SCSI Logical Unit (LUN), or an NVM Express namespace. It is the unit of persistent memory storage that appears in /dev as a device usable for I/O.

**Type:** defines the way in which the persistent memory associated with a Namespace or Region can be accessed. Valid Types are PMEM and BLK:

* **PMEM:** Direct access to the media via load/store operations. DAX Supported.
* **BLK:** Direct access to the media via Apertures (sliding memory windows). DAX is not supported.

**Mode:** defines which NVDIMM software features are enabled for a given Namespace. Namespace Modes include raw, sector, fsdax(memory), and devdax(dax). Sibling Namespaces of the same parent Region will always have the same Type, but might be configured to have different Modes.

## Configuration Options

This section discusses some of the common configuration options but does not cover all possible supported config.

Using one or more physical NVDIMMs, the available capacity can be configure in many different ways. Figure 1 below shows a typical Filesystem-DAX (FSDAX) configuration with three physical NVDIMMs that have been interleaved. All available capacity has been used to create a single region (Region0), namespace (Namespace0.0), and dax enabled filesystem created. Namespace naming convention is commonly X.Y where X is the region number and Y is the namespace. The persistent memory pool(s) are memory mapped to the application, thus allowing direct load/store access to the NVDIMMs.

![](https://1279085869-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvwSH5QpH0_ER83uxYK%2F-LvwkomCR1BL0VFpLSgN%2F-LvwlBtYw13PknzW_5Tx%2Fdraw.io-gitbook-interleaved-dimms-fsdax.jpg?alt=media\&token=5f2e188f-5683-4441-8e5d-2e2c75310589)

Figure 2 shows a configuration where the region has been partitioned into two namespaces. Each namespace has a single DAX Filesystem.

![](https://1279085869-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvwSH5QpH0_ER83uxYK%2F-LvwkomCR1BL0VFpLSgN%2F-LvwlFmTfOvpD8GUY9eA%2Fdraw.io-gitbook-interleaved-dimms-with-2-namespaces-fsdax%20\(1\).jpg?alt=media\&token=05d9d599-9773-470b-ba61-4bac6491b4d5)

Figure 3 shows a configuration where NVDIMM interleaving has been disabled. In this mode, each NVDIMM becomes addressable with single regions per device. Regions and Namespaces cannot be striped or interleaved across NVDIMMs. It is possible to use software RAID such as Linux's Device Mapper to implement mirroring, striping, or concatenation of the /dev/pmem{N} devices.

![](https://1279085869-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvwSH5QpH0_ER83uxYK%2F-LvwkomCR1BL0VFpLSgN%2F-LvwlSA1qHvOy6St0XnM%2Fdraw.io-gitbook-non-interleaved-dimm-fsdax.jpg?alt=media\&token=2ca8c490-07d3-4fd0-84c6-49cf2f5d3457)

The following sections describe each layer in more detail.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pmem.io/ndctl-user-guide/v69/concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.