drivers/crypto/intel/qat/qat_c62x

Intel QuickAssist (QAT) C62x Lewisburg crypto and compression accelerators

Hardware crypto and compression offload engines built into Intel's C620-series "Lewisburg" server chipsets, launched in 2017 alongside Xeon Scalable platforms. They accelerate bulk encryption, public-key crypto, and zlib-style compression for workloads like VPN gateways, TLS termination, and storage appliances.

keep-annotate conf=0.72 deploy=medium replacement=none subsystem=crypto category=crypto
72%

recommendation

Worth keeping but document its niche: the C62x family is now eight-year-old server silicon rather than current Intel hardware, yet upstream activity is healthy, with refactoring work and a device-specific shutdown fix landing as recently as May 2025. Intel still lists C62x among supported platforms for its current QAT Linux driver, so a sizeable installed base of Lewisburg-based servers continues to depend on it.

repository signals

4 files
464 source lines
18 commits, 5y
+505 / −38 lines added / removed, 5y
7 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 18 total · active in 11/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 1 commit · +431 −0 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +4 −8 2023-06: 3 commits · +35 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 2 commits · +2 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 1 commit · +1 −0 2024-04: 1 commit · +1 −1 2024-05: 0 commits · +0 −0 2024-06: 0 commits · +0 −0 2024-07: 1 commit · +2 −2 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 1 commit · +1 −1 2025-01: 0 commits · +0 −0 2025-02: 1 commit · +1 −1 2025-03: 4 commits · +27 −23 2025-04: 2 commits · +0 −2 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. git.kernel.org

    The directory had a substantive upstream change on 2025-05-05 ('crypto: qat - refactor compression template logic'), indicating current maintenance rather than abandonment.

  2. git.kernel.org

    The driver received a 2025 device-specific lifecycle fix ('add shutdown handler to qat_c62x'), which argues against deprecation/removal now.

  3. intel.com

    Intel's 2025 compatibility guidance still lists the Intel C62x Chipset among platforms using the current Intel QAT Linux CE driver, showing an active supported installed base.

  4. intel.com

    Intel ARK identifies C627 as a Lewisburg/C620-series server chipset launched in Q3'17 with integrated Intel QuickAssist Technology, supporting the assessment that this is older server hardware rather than a new 2025 platform.

codex reasoning notes (technical)

Local git history was obtained with shell `git log` (using safe.directory override); the two kernel.org commit URLs were then formed from those SHAs using canonical recall. Intel URLs were obtained via `web.search_query`. I also checked for lore-based removal signals first via `web.search_query` against `site:lore.kernel.org` for `qat_c62x`/directory terms and found no obvious removal discussion. Net: active upstream maintenance plus vendor support evidence suggests keep, but annotate as aging Lewisburg-era hardware with likely legacy/installed-base deployments rather than new mainstream 2025 sales.