drivers/nvme/target

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.

keep conf=0.96 deploy=medium replacement=none subsystem=nvme category=storage-block
96%

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

25 files
25,884 source lines
481 commits, 5y
+11,965 / −2,716 lines added / removed, 5y
102 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 481 total · active in 59/61 months
2021 2022 2023 2024 2025 2026 2021-04: 4 commits · +14 −8 2021-05: 17 commits · +48 −37 2021-06: 21 commits · +960 −161 2021-07: 3 commits · +18 −6 2021-08: 5 commits · +56 −24 2021-09: 10 commits · +79 −13 2021-10: 14 commits · +71 −18 2021-11: 6 commits · +36 −15 2021-12: 1 commit · +8 −1 2022-01: 3 commits · +23 −24 2022-02: 8 commits · +30 −32 2022-03: 10 commits · +85 −104 2022-04: 3 commits · +4 −5 2022-05: 3 commits · +4 −3 2022-06: 8 commits · +1,469 −47 2022-07: 15 commits · +42 −33 2022-08: 9 commits · +56 −42 2022-09: 17 commits · +116 −128 2022-10: 5 commits · +16 −11 2022-11: 12 commits · +174 −46 2022-12: 5 commits · +32 −27 2023-01: 4 commits · +10 −4 2023-02: 1 commit · +4 −11 2023-03: 13 commits · +95 −88 2023-04: 3 commits · +28 −31 2023-05: 4 commits · +2 −8 2023-06: 5 commits · +34 −21 2023-07: 1 commit · +3 −3 2023-08: 9 commits · +467 −46 2023-09: 1 commit · +12 −9 2023-10: 10 commits · +38 −35 2023-11: 5 commits · +13 −5 2023-12: 12 commits · +80 −45 2024-01: 26 commits · +209 −126 2024-02: 4 commits · +101 −5 2024-03: 3 commits · +13 −13 2024-04: 10 commits · +156 −77 2024-05: 13 commits · +395 −30 2024-06: 7 commits · +150 −131 2024-07: 3 commits · +20 −8 2024-08: 4 commits · +16 −4 2024-09: 2 commits · +3 −4 2024-10: 6 commits · +166 −42 2024-11: 14 commits · +1,604 −24 2024-12: 5 commits · +93 −69 2025-01: 21 commits · +3,448 −137 2025-02: 13 commits · +355 −142 2025-03: 11 commits · +54 −75 2025-04: 24 commits · +304 −200 2025-05: 22 commits · +392 −223 2025-06: 6 commits · +11 −7 2025-07: 5 commits · +32 −21 2025-08: 2 commits · +5 −6 2025-09: 8 commits · +50 −46 2025-10: 5 commits · +31 −32 2025-11: 5 commits · +16 −14 2025-12: 4 commits · +26 −5 2026-01: 4 commits · +23 −4 2026-02: 7 commits · +165 −180 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. 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.

  2. 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.

  3. 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.

  4. docs.oracle.com

    Oracle Database 26 documentation instructs configuring Linux NVMe-oF storage targets using `nvmet_tcp` and `nvmetcli`, indicating active real deployments.

  5. 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.