CCR(4)

📦 version 12.2, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 ccr(4) — Chelsio T6 crypto accelerator driver 💖

okay bestie, sit down, hydrate, because this is the manual page for ccr(4) from the Kernel Interfaces Manual and it is genuinely iconic. this is the driver that makes your Chelsio T6 card go brrrr on crypto so your CPU can chill. let's get into it 🦋

✨ NAME ✨

ccr — the Chelsio T6 crypto accelerator driver. that's it, that's the name, she's simple and she knows it 💅

✨ SYNOPSIS ✨

so you wanna bake this driver into the kernel? not as a module, but all the way in? then bestie you need to drop these lines into your kernel configuration file:

device ccr
device cxgbe

both. yes, both. the second one is not optional, i'll explain in a sec 🫶

orrrr, if you'd rather load it as a module at boot time (very main character of you), you put this line in loader.conf(5):

ccr_load="YES"

boom. that's the whole vibe check. ✨

✨ DESCRIPTION ✨

okay so the ccr driver provides support for the crypto accelerator engine that's included on PCI Express Ethernet adapters based on the Chelsio Terminator 6 ASIC (T6). say that three times fast. 🌀

and what does that engine actually do? it accelerates a whole roster of operations for crypto(4) and ipsec(4). here's the lineup, and yes, we're listing all of them, no skips:

  • AES-CBC
  • AES-CCM
  • AES-CTR
  • AES-GCM
  • AES-XTS
  • SHA1
  • SHA2-224
  • SHA2-256
  • SHA2-384
  • SHA2-512
  • SHA1-HMAC
  • SHA2-224-HMAC
  • SHA2-256-HMAC
  • SHA2-384-HMAC
  • SHA2-512-HMAC

that's fifteen. the whole girl group. 👑

and she doesn't just do them one at a time — the driver also supports chaining one of AES-CBC, AES-CTR, or AES-XTS with one of SHA1-HMAC, SHA2-224-HMAC, SHA2-256-HMAC, SHA2-384-HMAC, or SHA2-512-HMAC for encrypt-then-authenticate operations. it's giving collab era 🤝

for further hardware information and questions related to hardware requirements, go look at http://www.chelsio.com/ — that's the plug, iykyk.

okay and here's the part that matters: the ccr driver attaches as a child of an existing Chelsio NIC device. meaning she literally requires that the cxgbe(4) driver be active. no cxgbe, no ccr. she does not exist in a vacuum, she's a nepo baby of the NIC driver, and honestly? respect. 😌

✨ HARDWARE ✨

the ccr driver supports the crypto accelerator engine included on adapters based on the T6 ASIC, which is:

  • Chelsio T6225-CR
  • Chelsio T6225-SO-CR
  • Chelsio T62100-LP-CR
  • Chelsio T62100-SO-CR
  • Chelsio T62100-CR

five cards. check yours before you come crying to the group chat 🙈

✨ SUPPORT ✨

for general information and support, go to the Chelsio support website at: http://www.chelsio.com/

and if you've identified an issue with this driver with a supported adapter, email all the specific information related to the issue to ⟨support@chelsio.com⟩. "all the specific information" — not "it broke", bestie. give them the details. 💖

✨ SEE ALSO ✨

✨ HISTORY ✨

the ccr device driver first appeared in FreeBSD 12.0. a legend was born. 🌸

✨ AUTHORS ✨

the ccr driver was written by John Baldwin <jhb@FreeBSD.org>. thank you for your service, king 👑

and that's the whole page, bestie!! 🎀 this one came to you from Debian, dated June 3, 2019, filed under CCR(4) — so go forth, chain your AES-XTS with your SHA2-512-HMAC, and let the T6 do the heavy lifting. no cap. periodt. 💜🦋✨

📦 where this page comes from