NVMe over Fabrics target stack (TCP, RDMA, FC, PCI-EPF, passthrough)
Server-side implementation of NVMe over Fabrics, letting a Linux machine export local NVMe storage to remote initiators over TCP, RDMA, Fibre Channel, or a PCI endpoint. It is the backbone of modern disaggregated storage in enterprise arrays and data centers built on 2020s-era smart NICs and NVMe SSDs.
recommendation
It should stay because this is the kernel's only in-tree NVMe-oF target and remains under active development, with fixes landing in nvmet-tcp as recently as January 2026. Enterprise distributions like SUSE ship it, Oracle Database 26 documents configuring storage targets on top of it, and NVIDIA's ConnectX-5+ offload path relies on the same in-kernel stack, so it underpins shipping 2025 hardware and real production deployments.
repository signals
sources
- kernel.googlesource.com
A 2026-01-13 upstream commit fixes `drivers/nvme/target/tcp.c`, showing current maintenance activity in the target stack rather than retirement.
- docs.kernel.org
Official kernel documentation describes the NVMe PCI Endpoint Function Target built on the NVMe target core, with current setup and hardware requirements.
- documentation.suse.com
SUSE enterprise documentation describes NVMe-oF host and target support and states kernel modules are available for the NVMe-oF target and host.
- docs.oracle.com
Oracle Database 26 documentation instructs configuring Linux NVMe-oF storage targets using `nvmet_tcp` and `nvmetcli`, indicating active real deployments.
- docs.nvidia.com
NVIDIA networking documentation describes NVMe-oF target offload on ConnectX-5 and newer adapters and notes use of the inbox `nvme-tcp` kernel module, tying the stack to current shipping hardware.
codex reasoning notes (technical)
This is an active in-kernel target driver directory, not a legacy leaf: local shell inspection of `drivers/nvme/target/Kconfig` and `Documentation/nvme/nvme-pci-endpoint-target.rst` shows current TCP/RDMA/FC/PCI-EPF/passthrough functionality, and local grep found it enabled in current defconfigs. URLs were obtained via web search. The 2026 googlesource commit page includes a lore link and demonstrates recent upstream fixes in `nvmet-tcp`; no removal/deprecation discussion surfaced in the web searches I ran, so there is no basis to escalate beyond `keep`. Deployment looks medium rather than high: this is enterprise/storage-appliance and specialized embedded/PCI-endpoint infrastructure, not consumer hardware, but it remains relevant for new 2025-era deployments and modern NIC/storage platforms. No natural upstream replacement driver covers the same in-kernel NVMe target role.