NVMe base specification
The NVM Express Base Specification is the transport-independent core NVMe document defining controller properties, admin commands, queues and common I/O command-set aspects.
The NVMe interface lets a host reach a non-volatile memory subsystem over PCI Express, Ethernet, InfiniBand, Fibre Channel and other transports, each mapped in a separate transport binding. The base document defines properties and commands for I/O, discovery and administrative controllers, and leaves media management such as wear leveling and caching algorithms out. [2]
It is one of eleven specifications in the 2.4 set, with command sets such as key value, zoned namespaces and computational programs and transports such as PCIe, RDMA and TCP published separately. [3] [2]
Revision 2.4 (July 2026) allows up to 65,535 I/O queues with up to 65,535 outstanding commands each, 64-byte submission entries, completion entries of at least 16 bytes and one to 64Ki - 16 controllers per subsystem. [2] The Linux kernel encodes the I/O submission entry size as 2^6 = 64 bytes and the opcodes flush 0x00, write 0x01 and read 0x02, and admin identify 0x06, create submission queue 0x01 and create completion queue 0x05. [4]
Relations
Advantages
- A 64-byte command carries everything needed for a 4 KiB read. [2]
- Host software can reuse admin and I/O command logic when only the transport binding changes. [2]
Limitations
- The document runs to 870 pages and is revised several times a year, so claims need a revision number to be checkable. [2, 3]
- Queue and controller limits are architectural maxima, not what any real device implements. [2]
Citations
- NVM Express Base Specification, Revision 2.4, 31 July 2026.
- NVM Express. Base Specification landing page and revision list.
- Linux kernel source: include/linux/nvme.h.
Further reading
Sources & caveats
- All figures are from the standards body's own text (revision 2.4, released 4 August 2026), not from device measurements.
- Older descriptions tie the base document to PCIe only; when the transport split happened was not verified, as older revisions were not read.
- Reading and citing the specification is open to non-members; implementing it requires membership terms.
- The page count comes from the PDF metadata; the kernel header is a master-branch snapshot on the access date.