drivers/scsi/elx/efct

Emulex LPe31000/LPe36000 Fibre Channel Target Mode HBAs

Target-mode support for Broadcom/Emulex Gen 6 and Gen 7 Fibre Channel host bus adapters, including the LPe31004 (32 Gb) and LPe36000 (64 Gb) families. These cards sit in storage arrays and similar appliances, letting a Linux server present itself as a Fibre Channel storage target to SAN clients rather than as an initiator.

keep conf=0.89 deploy=medium replacement=none subsystem=scsi category=storage-scsi-ata
89%

recommendation

It should stay in the kernel because the underlying hardware is current: Broadcom still actively sells both the LPe31000 and LPe36000 Emulex HBA lines in 2025, and the code itself has seen substantive commits through mid-2025 with no removal discussion on the kernel mailing lists. This is mainstream, in-production enterprise storage hardware with an engaged vendor.

repository signals

15 files
11,306 source lines
49 commits, 5y
+11,456 / −150 lines added / removed, 5y
24 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 49 total · active in 20/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 22 commits · +11,361 −24 2021-07: 0 commits · +0 −0 2021-08: 3 commits · +5 −8 2021-09: 2 commits · +3 −4 2021-10: 1 commit · +1 −2 2021-11: 0 commits · +0 −0 2021-12: 1 commit · +7 −7 2022-01: 1 commit · +4 −7 2022-02: 0 commits · +0 −0 2022-03: 1 commit · +0 −1 2022-04: 0 commits · +0 −0 2022-05: 2 commits · +0 −4 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 1 commit · +1 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 2 commits · +1 −21 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +5 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 1 commit · +1 −0 2024-07: 0 commits · +0 −0 2024-08: 1 commit · +2 −1 2024-09: 0 commits · +0 −0 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 1 commit · +1 −1 2025-01: 1 commit · +1 −1 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 1 commit · +2 −2 2025-05: 1 commit · +1 −1 2025-06: 2 commits · +4 −3 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 1 commit · +1 −7 2026-02: 3 commits · +55 −56 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. cateee.net

    CONFIG_SCSI_EFCT is the in-tree efct module for Emulex Fibre Channel Target, present through current kernel heads, and matches PCI IDs 10df:e307 and 10df:f407 used by this driver.

  2. docs.broadcom.com

    Broadcom's current Emulex Fibre Channel HBA product guide still lists both LPe36000 and LPe31000 families, indicating ongoing product-line support and market presence.

  3. docs.broadcom.com

    A 2025-published Broadcom product brief documents the LPe36000-series as current Gen 7 Fibre Channel HBAs.

  4. investors.broadcom.com

    Broadcom announced immediate availability of the Emulex Gen 7 LPe36000-series in 2021, aligning with the driver's LPE36000 device string.

  5. docs.broadcom.com

    Broadcom product brief for LPe31004/LPe32000 documents LPe31004-M6 models, aligning with the driver's LPE31004 device string.

codex reasoning notes (technical)

Local shell inspection of efct_driver.c and efct_hw.h showed this is a real PCI FC target driver for Emulex/Broadcom devices e307/f407, with model strings LPE31004 and LPE36000. Local shell git log (git -c safe.directory=... log -- drivers/scsi/elx/efct) showed substantive upstream activity through 2025-06-27 and 2026-01-28 plus treewide touches in 2026, so maintenance is active rather than dormant. Web search on lore.kernel.org queries for efct/removal returned no hits, so I found no evidence of an active upstream removal series. URLs were obtained via web search; the kernel activity evidence came from local shell commands. Because Broadcom still publishes current product material covering both supported families and the driver is actively maintained, this is not a deprecation candidate.