NVM subsystem
An NVMe system containing one or more controllers, domains and ports, with zero or more namespaces.
The subsystem is broader than an individual controller and need not expose a storage namespace. For example, a Discovery Service contains only Discovery controllers and does not expose namespaces. [1]
Over fabrics, a subsystem presents from one to 64Ki minus 16 controllers, reached through one to 64Ki subsystem ports. Each port has a 16-bit port identifier and is named by the subsystem qualified name together with that identifier. Aggregated physical links count as one port, and once connected each controller is bound to a single port. [1]
Multi-path I/O and namespace sharing both require two or more controllers in the subsystem. Controllers that share a namespace use the same namespace identifier for it, and coordination between hosts that access it concurrently is outside the scope of the specification. [1]
The subsystem qualified name is permanent for the lifetime of the subsystem and is a null-terminated UTF-8 string of at most 223 bytes. An open-source host library reserves a 256-byte field for it and stores the controller identifier in a 16-bit field. [1] [2]
Relations
Advantages
- Several controllers and ports in one subsystem give a host independent paths to the same shared namespace. [1]
Limitations
- The specification does not define how hosts coordinate concurrent access to a shared namespace. [1]
Citations
- NVM Express Base Specification 2.1 (5 August 2024), sections 1.5, 2.2.2, 2.4.1 and 4.7. Copyright 2008-2024 NVM Express, Inc. All rights reserved.
- libnvme v1.13: NVMe qualified-name length and controller identifier definitions
Sources & caveats
- base21 was reread on the access date in sections 1.5, 2.2.2, 2.4.1 and 4.7.
- libnvme-types is the types header of the open-source host library at tag v1.13, read for the qualified-name length constant and the controller identifier fields.
- 64Ki minus 16 controllers, 64Ki ports, the 16-bit port identifier and 223 bytes come from base21. 256 bytes and the 16-bit controller identifier field come from libnvme-types.