drivers/ntb

PCIe Non-Transparent Bridge (NTB) core and vendor backends

PCIe Non-Transparent Bridges let two or more independent computers share a PCI Express fabric while keeping their memory spaces isolated, exposing controlled doorbells and memory windows so the hosts can exchange data. They are used in specialized multi-host server, storage, and embedded designs, with hardware from Intel, AMD, IDT, and Microchip's Switchtec PCIe switches.

keep conf=0.84 deploy=low replacement=none subsystem=ntb category=bus-pci
84%

recommendation

It should stay because this is the generic framework that all the vendor-specific NTB drivers (Intel, AMD, IDT, Microchip Switchtec) plug into, and there is no in-tree replacement. Although deployments are niche rather than mass-market, the code is actively maintained — core.c received new feature work in early 2026 (driver_override support) — and Microchip still sells current Gen 5 and Gen 6 PCIe switches advertising NTB capability, so the subsystem remains relevant for specialized multi-host systems.

repository signals

36 files
19,457 source lines
82 commits, 5y
+581 / −476 lines added / removed, 5y
47 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 82 total · active in 33/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 3 commits · +5 −2 2021-07: 1 commit · +2 −6 2021-08: 1 commit · +6 −33 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 10 commits · +32 −24 2022-01: 2 commits · +34 −5 2022-02: 1 commit · +35 −13 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 2 commits · +8 −6 2022-08: 1 commit · +16 −5 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 5 commits · +21 −4 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 4 commits · +9 −24 2023-04: 1 commit · +2 −4 2023-05: 1 commit · +1 −1 2023-06: 0 commits · +0 −0 2023-07: 2 commits · +1 −3 2023-08: 8 commits · +25 −24 2023-09: 0 commits · +0 −0 2023-10: 1 commit · +1 −1 2023-11: 0 commits · +0 −0 2023-12: 2 commits · +8 −2 2024-01: 1 commit · +5 −3 2024-02: 0 commits · +0 −0 2024-03: 1 commit · +1 −1 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 2 commits · +4 −1 2024-07: 2 commits · +4 −4 2024-08: 0 commits · +0 −0 2024-09: 4 commits · +21 −9 2024-10: 1 commit · +9 −4 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 1 commit · +1 −1 2025-02: 6 commits · +19 −80 2025-03: 4 commits · +31 −36 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 2 commits · +68 −50 2025-08: 1 commit · +7 −0 2025-09: 1 commit · +18 −1 2025-10: 3 commits · +108 −19 2025-11: 1 commit · +0 −1 2025-12: 1 commit · +1 −1 2026-01: 4 commits · +77 −104 2026-02: 1 commit · +1 −1 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    `drivers/ntb/core.c` saw upstream feature work in January 2026 ('NTB: core: Add driver_override support for NTB devices'), so the subsystem is still maintained rather than abandoned.

  2. docs.kernel.org

    Kernel documentation describes NTB as a current PCIe bridge class and `ntb` as the core framework used by hardware-specific NTB drivers and clients, confirming this directory is the active generic core for the subsystem.

  3. microchip.com

    Microchip's current Switchtec PCIe switch portfolio page lists Gen 5 and Gen 6 products and explicitly advertises up to 48 Non-Transparent Bridges (NTBs), showing NTB-capable hardware was still sold new in and after 2025.

codex reasoning notes (technical)

`drivers/ntb` is the generic NTB core/framework, with vendor backends under `drivers/ntb/hw/` (Intel, AMD, IDT, Microchip Switchtec). Recent lore activity on `core.c` from `lore_file_timeline` shows live upstream development in 2026, which argues strongly against deprecation/removal. Deployment is niche rather than mass-market, so I marked it `low`, but current Microchip Switchtec products indicate NTB remains relevant for specialized server/storage/embedded multi-host designs. No natural in-tree replacement exists for the NTB core API. Source acquisition: lore URL via `lore_file_timeline`; docs.kernel.org URL identified from local `Documentation/driver-api/ntb.rst` and confirmed via `web.search_query`; Microchip product URL obtained via `web.search_query`.