Lucas and Luna dive into the Linux Kernel Crypto API, the subsystem that offloads encryption, decryption, and hashing to hardware accelerators like Intel QAT, AMD CCP, and ARM CryptoCell. They unpack how the API abstracts vendor-specific drivers behind a unified interface, enabling applications like dm-crypt (LUKS disks), IPsec, and TLS termination in the kernel to transparently use hardware crypto without user-space changes. The episode focuses on a specific example: how switching from software AES to hardware-accelerated AES on an Intel Xeon with QAT can reduce CPU load by over 80 percent while maintaining wire-speed throughput. Lucas explains the async request model, the role of cryptographic operation vectors (crypto_async_request), and how the crypto manager handles fallback to software if hardware is unavailable. Luna asks about real-world deployment gotchas — like driver maturity, NUMA affinity, and the trade-off between latency and throughput in synchronous vs. asynchronous paths. They also touch on how the same API powers kernel TLS (KTLS) for Netflix-scale content delivery. No marketing fluff — just a clear, technical look at a subsystem that quietly improves performance and security across millions of Linux servers.