drivers/net/ethernet/mellanox/mlx5/core/sf/dev

NVIDIA Mellanox mlx5 Scalable Function auxiliary devices

Scalable Functions are a lightweight virtualization mechanism on NVIDIA Mellanox ConnectX and BlueField networking hardware, letting one physical adapter expose many independent network interfaces to containers, VMs, or DPU workloads without full SR-IOV overhead. They are common in modern datacenters and BlueField-2/3 DPUs and SmartNICs.

keep conf=0.92 deploy=medium replacement=none subsystem=net category=networking-ethernet
92%

recommendation

It should stay because the underlying ConnectX and BlueField-3 hardware is actively sold by NVIDIA in 2025, the SF deployment model is documented in current NVIDIA DOCA guides, and upstream patch traffic touching this code is still landing as recently as late 2025 and early 2026. There is no replacement driver upstream, and SR-IOV is an architectural alternative rather than a substitute.

repository signals

4 files
680 source lines
33 commits, 5y
+370 / −122 lines added / removed, 5y
12 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 33 total · active in 22/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 1 commit · +1 −1 2021-06: 1 commit · +1 −0 2021-07: 0 commits · +0 −0 2021-08: 1 commit · +1 −1 2021-09: 1 commit · +2 −0 2021-10: 2 commits · +77 −10 2021-11: 0 commits · +0 −0 2021-12: 1 commit · +1 −4 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 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: 0 commits · +0 −0 2022-08: 1 commit · +88 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 1 commit · +1 −1 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 1 commit · +1 −0 2023-05: 1 commit · +13 −2 2023-06: 5 commits · +6 −21 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +32 −0 2023-10: 1 commit · +57 −29 2023-11: 0 commits · +0 −0 2023-12: 1 commit · +5 −4 2024-01: 1 commit · +13 −8 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 2 commits · +0 −2 2024-05: 2 commits · +9 −12 2024-06: 0 commits · +0 −0 2024-07: 1 commit · +1 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 1 commit · +1 −1 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 2 commits · +41 −18 2025-12: 0 commits · +0 −0 2026-01: 1 commit · +1 −0 2026-02: 2 commits · +6 −6 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. spinics.net

    A net-next patch posted on 2025-11-16 updates SF dev-table notifier registration for mlx5, showing ongoing upstream work in this area rather than retirement.

  2. spinics.net

    A net patch posted on 2026-01-20 fixes an mlx5 initialization bug in the same subsystem window, consistent with active maintenance through 2026.

  3. docs.nvidia.com

    NVIDIA's 2026 BlueField SF guide documents creating, configuring, and deploying `mlx5_core.sf.*` auxiliary devices, showing SF is a current supported deployment model.

  4. docs.nvidia.com

    The BlueField-3 platform guide lists BlueField-3 DPU and SuperNIC SKUs/specifications, indicating the underlying mlx5 hardware family is still a current product line.

codex reasoning notes (technical)

Local shell inspection of `driver.c` shows a real `auxiliary_driver` for `mlx5_core.sf`, not a helper library. Local `git -c safe.directory=... log` shows substantive touches through 2026-01-29. Web search was used because `lei` is unavailable here: spinics/netdev results show active 2025-11 and 2026-01 patch traffic touching this SF area, and I found no removal/deprecation thread in the same searches. NVIDIA docs found by web search show SF deployment instructions in 2026 and current BlueField-3 DPU/SuperNIC SKUs, so this is still sold and deployed, but mainly in datacenter/DPU/SmartNIC niches rather than mass commodity systems. No direct replacement upstream driver exists; SR-IOV VFs are an architectural alternative, not a driver replacement.