> For the complete documentation index, see [llms.txt](https://docs.pmem.io/ndctl-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pmem.io/ndctl-user-guide/v71/master.md).

# NDCTL User Guide

## Introduction

`ndctl` is a utility for managing the Linux LIBNVDIMM Kernel subsystem. It is designed to work with various non-volatile memory devices (NVDIMMs) from different vendors. The LIBNVDIMM subsystem defines a kernel device model and control message interface for platform NVDIMM resources like those defined by the [ACPI v6.0](http://www.uefi.org/sites/default/files/resources/ACPI_6_0_Errata_A.PDF) NFIT (**N**VDIMM **F**irmware **I**nterface **T**able). The latest [ACPI ](http://www.uefi.org/specifications)and [UEFI ](http://www.uefi.org/specifications)specifications can be found at [uefi.org](http://www.uefi.org). Operations supported by `ndctl` include:

* Provisioning capacity (namespaces)
* Enumerating Devices
* Enabling and Disabling NVDIMMs, Regions, and Namespaces
* Managing NVDIMM Labels

## What's new in v71

This release incorporates functionality up to the 5.10 kernel.

Highlights include support for the new device-dax subdivision functionality added in Linux in v5.10, including ways to create smaller devdax devices using daxctl/libdaxctl, as well as creating, listing, and restoring from a config dump, 'mappings' on these devices. Other updates include several static analysis fixups, reworking the license identification scheme for different sub-components, and a fix for the reconfigure-in-place workflow which tries to retain device names.

Commands:&#x20;

* daxctl-create-device: new command&#x20;
* daxctl-destroy-device: new command&#x20;
* daxctl-enable-device: new command&#x20;
* daxctl-disable-device: new command&#x20;
* daxctl-reconfigure-device: allow resizing devices&#x20;
* ndctl-create-namespace: improve reconfigure in-place

Tests:&#x20;

* daxctl-create.sh: new test for device-dax subdivision

APIs:&#x20;

* daxctl\_dev\_get\_align&#x20;
* daxctl\_dev\_set\_align&#x20;
* daxctl\_dev\_set\_mapping
* daxctl\_dev\_set\_size&#x20;
* daxctl\_mapping\_get\_end&#x20;
* daxctl\_mapping\_get\_first&#x20;
* daxctl\_mapping\_get\_next&#x20;
* daxctl\_mapping\_get\_offset&#x20;
* daxctl\_mapping\_get\_size&#x20;
* daxctl\_mapping\_get\_start&#x20;
* daxctl\_region\_create\_dev&#x20;
* daxctl\_region\_destroy\_dev


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.pmem.io/ndctl-user-guide/v71/master.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
