Intel QuickAssist Technology Gen4 accelerators (4xxx, 401xx, 402xx)
Intel's fourth-generation QuickAssist Technology accelerators are PCIe offload engines for bulk symmetric crypto, public-key crypto, and lossless compression, integrated into 4th and 5th Generation Xeon Scalable server CPUs (PCI IDs 8086:4940/4942/4944 plus the 401xx and 402xx variants). They are widely used in datacenters to speed up TLS termination, VPN/IPsec, and storage compression workloads.
recommendation
It should stay in the kernel because this is the in-tree driver for Intel's current-generation QuickAssist crypto and compression accelerators, which are integrated into 4th and 5th Generation Xeon Scalable platforms still being sold and deployed in 2025. Upstream activity is healthy (over 50 substantive commits in the last five years, with changes landing as recently as mid-2025), and Intel's own QATlib and support documentation continue to direct users to this exact module.
repository signals
sources
- cateee.net
`CONFIG_CRYPTO_DEV_QAT_4XXX` is present in current upstream kernel series and binds PCI IDs 8086:4940/4942/4944 to `qat_4xxx`.
- intel.github.io
Intel's current QATlib requirements list 4xxx, 401xx, and 402xx as supported devices using the `qat_4xxx` kernel module, alongside newer 420xx parts using `qat_420xx`.
- intel.com
Intel support documentation reviewed on 2025-09-10 still instructs users to load the in-tree `intel_qat` and `qat_4xxx` modules, indicating active field use/support.
- intel.com
Intel's 2026 Hardware Version 2.0 driver page validates 4xxx/401xx/402xx accelerators against 4th and 5th Gen Xeon platforms, showing the hardware family remains in supported deployments.
codex reasoning notes (technical)
Real PCI driver confirmed locally via `rg` on Kconfig/Makefile/adf_drv.c (`MODULE_DEVICE_TABLE`, Intel PCI IDs 4940/4942/4944). Prompt metadata already shows strong recent upstream activity (54 substantive commits in 5y, latest 2025-07-18), which argues against deprecation. I attempted lore-first checks, but the advertised lore MCP server was unavailable and `lei` was not installed; web searches on lore/kernel terms produced no removal/deprecation thread hits, so I found no evidence of active upstream removal talk. URLs were obtained via web search/open (`web.search_query`, `web.open`, `web.find`). Overall this is a current datacenter accelerator driver with ongoing kernel and vendor support; keep it.