Intel In-Memory Analytics Accelerator (IAA) crypto offload
An on-die accelerator built into recent Intel Xeon Scalable server processors (4th and 5th Gen) that offloads compression, decompression, and analytics-style data transformations from the CPU cores. The kernel piece exposes it through the crypto framework so that workloads like database engines, storage stacks, and memory tiering can hand off DEFLATE-style work to dedicated hardware.
recommendation
It should stay in the kernel because IAA is a current-generation feature built into 4th and 5th Gen Intel Xeon Scalable server CPUs, the MAINTAINERS file marks the driver as Supported, and patch traffic on the kernel list continued through late 2025. No replacement driver exists for the same hardware, and Intel is still shipping the silicon in new servers in 2025.
repository signals
sources
- kernel.org
The kernel MAINTAINERS entry lists INTEL IAA CRYPTO DRIVER as Supported and covers drivers/crypto/intel/iaa/*.
- spinics.net
Public patch traffic for this driver continued in late 2025, showing active upstream bug-fix attention rather than removal.
- intel.com
Intel markets IAA as a built-in accelerator in Xeon Scalable processors for compression/decompression and analytics workloads.
- intel.com
Intel support documentation reviewed on February 9, 2026 lists IAA as available on 5th Gen Xeon Scalable processor SKUs, indicating ongoing current-platform availability.
codex reasoning notes (technical)
Local shell inspection of drivers/crypto/intel/iaa/Kconfig and git log shows a real kernel driver, introduced recently and still receiving substantive fixes through late 2025. The kernel.org MAINTAINERS page was obtained via web search/open and marks the area Supported. The spinics patch URL was obtained via web search for recent 'crypto: iaa' traffic and shows active maintenance; no removal/deprecation discussion surfaced in the allotted searches. Intel product/support URLs were obtained via web search/open and show IAA is part of current Xeon server offerings, so this is not legacy-only hardware. Because the driver is young, maintained, and tied to still-sold server CPUs, the recommendation is keep; there is no natural upstream replacement driver for the same hardware offload role.