Hardware cryptographic accelerator drivers
A collection of Linux drivers for hardware that offloads cryptographic work — encryption, hashing, signing, random-number generation — from the CPU. It covers everything from Intel QuickAssist accelerators in current Xeon servers, to IBM Z mainframe Crypto Express cards, to small SoC crypto engines in ARM systems, plus the virtio-crypto device used by virtual machines.
recommendation
It should stay in the kernel because this directory is an umbrella for dozens of actively used cryptographic accelerators, not a single aging chipset. Intel still ships QuickAssist on 4th-gen Xeon Scalable CPUs, IBM still sells Crypto Express 8S / 4770 cards for current z16 and z17 mainframes, and the virtio-crypto entries serve modern VM guests, so the subtree as a whole is firmly in production use.
repository signals
sources
- git.kernel.org
Current upstream Kconfig shows this directory is an umbrella for many hardware crypto drivers across x86, s390, SoC and virtual devices, not a single aging chipset.
- intel.com
Intel still markets QuickAssist Technology for current data-center, cloud, storage and networking deployments.
- intel.com
Intel states 4th Gen Intel Xeon Scalable processors support Intel QAT acceleration, indicating ongoing new-platform deployment.
- ibm.com
IBM documents Crypto Express8S / 4770 availability on IBM Z z16 and z17 and on Linux on IBM Z, showing current hardware covered by this subtree is still sold/deployed.
- docs.oasis-open.org
Virtio 1.3 defines a virtio crypto device type, supporting continued VM/guest deployment relevance for the virtio portion of this directory.
codex reasoning notes (technical)
Recommendation is for the subtree as a whole, not any one legacy leaf driver. lore-http `lore_file_timeline` on `drivers/crypto/` returned zero exact path matches, so there was no positive evidence of a subtree-wide removal series; two broader `lore_regex` subject probes timed out, so I did not treat them as removal evidence. Local shell inspection of `drivers/crypto/Kconfig` showed a broad, current umbrella of active hardware and virtual crypto engines. The kernel.org Kconfig URL is canonical recall matching the locally inspected file; Intel, IBM, and OASIS URLs were obtained via web search. Because the directory spans actively sold server/mainframe/SoC/virtual hardware and already shows heavy recent upstream churn in the provided stats, this should be kept rather than deprecated; there is no single replacement driver for the whole subtree.