UNION SLC_STORE_INFO(9)

💅 union slc_store_info(9) — a Kernel API Manual moment

okay bestie so we're in the Kernel API Manual today and the star of the show is union slc_store_info 💖 it lives over in ./drivers/crypto/cavium/nitrox and honestly she's giving "quiet little union that holds the receipts for solicited packet output store info" energy ✨

---

✨ NAME ✨

union slc_store_info — Solicited Paceket Output Store Information.

(and yes it says "Paceket" 😭 that's literally what the page says, we don't touch it, we respect the typo's main character moment 🫶)

---

🎀 SYNOPSIS 🎀

union slc_store_info {
    __be64 bev[2];
    u64 value[2];
    struct {
  #if defined(__BIG_ENDIAN_BITFIELD);
      u64 raz_39_63 : 25;
      u64 ssz : 7;
      u64 raz_0_31 : 32;
  #else;
      u64 raz_0_31 : 32;
      u64 ssz : 7;
      u64 raz_39_63 : 25;
  #endif;
      __be64 rptr;
    } s;
 };

so she's a union, she's got range 💁‍♀️ you can peek at her as two __be64 in bev[2], or as two u64 in value[2], or dive into the anonymous-ish struct s — which is lowkey the icon of the whole page:

• u64 raz_39_63 : 25; — 25 bits of raz_39_63, and ngl the name is telling you exactly which bits it's holding down 🔥
• u64 ssz : 7; — 7 whole bits of pure ssz slay, sitting right in the middle of the lineup ✨
• u64 raz_0_31 : 32; — 32 bits of raz_0_31, doing its thing 🌸
• __be64 rptr; — and then rptr, a whole __be64, no bitfield games, just vibes 👑

and the way the bitfield order flips depending on the #if defined(__BIG_ENDIAN_BITFIELD); check?? that's the structural equivalent of knowing which side of the group photo is your good side 😌 raz_0_31 and raz_39_63 literally swap positions between the big-endian branch and the #else; branch, while ssz and rptr stay exactly where they belong. periodt. 💅

---

🦋 Members 🦋

this section is… empty, bestie 💀 like genuinely nothing is listed under it. so there's nothing to report, we just hold space for her, we let her breathe 🙈

---

🌈 SEE ALSO 🌈

the friend group 👯‍♀️ all of these are from the kernel file ./drivers/crypto/cavium/nitrox/nitrox_req.h:

• struct gphdr(9)
• union se_req_ctrl(9)
• struct se_crypto_request(9)
• struct crypto_keys(9)
• struct auth_keys(9)
• struct flexi_crypto_context(9)
• struct nitrox_aead_rctx(9)
• struct nitrox_rfc4106_rctx(9)
• union pkt_instr_hdr(9)
• union pkt_hdr(9)
• struct nps_pkt_instr(9)
• struct aqmq_command_s(9)
• struct ctx_hdr(9)
• struct nitrox_softreq(9)
• create_single_sg(9)
• create_multi_sg(9)

like okayyy look at that lineup, that's a whole friend group chat and every single one of them is invited to the function 🎉

---

💖 real talk: everything above is straight from the page, no cap. any time you're poking at union slc_store_info, remember she's shared storage — the fields overlap, that's the whole point of a union, so treat the bitfield layout with the respect it deserves ✨

---

and that's the whole page, bestie 🫶 brought to you by ./drivers/crypto/cavium/nitrox, dated October 2026, filed under union slc_store_info(9) — she's iconic, she's niche, she's a crypto driver union, and she ate 💅👑⭐