Intel's high-end datacenter Ethernet controllers in the E800 family, covering the E810, E822/E823, and newer E830/E835 chips that drive 10/25/50/100 GbE PCIe server NICs introduced from around 2019 onward. These cards are widely used in modern cloud, storage, and HPC servers and support advanced offloads such as RDMA, DCB, and SR-IOV.
It should stay in the kernel because this is the active driver for Intel's current-generation server Ethernet silicon, with more than 1,300 commits from nearly 200 authors over the last five years and ongoing additions of new PCI IDs for the newer E830 and E835 parts. Intel is still selling E810 adapters as launched products, and no replacement driver exists.
repository signals
127files
125,335source lines
1,397commits, 5y
+115,450 / −55,258lines added / removed, 5y
206authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 1,397 total · active in 60/61 months
LKDDb shows CONFIG_ICE is current through Linux 7.0 and covers many actively supported Intel E800-family PCI IDs, including E810, E822/E823, E830, and E835 devices.
Intel shows a concrete E810 adapter SKU as 'Launched' with current specifications, indicating the hardware remained a live shipping product line beyond 2025.
codex reasoning notes (technical)
This is plainly a real PCI Ethernet driver: prompt metadata shows module-driver markers, 50 C files, 1352 substantive commits in 5 years, 188 authors, and most recent substantive touch on 2026-04-06, which is strong evidence against deprecation. Local shell `rg` confirmed the directory is the in-tree 'Intel(R) Ethernet Connection E800 Series' driver. `web search` found LKDDb's CONFIG_ICE page showing the driver is still built in current kernels and has gained newer E830/E835 PCI IDs, which indicates ongoing upstream expansion rather than retirement. `web search` also found Intel's E810 family page and a launched E810 adapter SKU page, supporting that hardware is still sold for server/datacenter deployments. A direct `web search` for lore removal/deprecation discussion returned no hits; combined with the very recent activity, that argues strongly for keep. No natural replacement driver exists upstream for the same hardware family.