STRUCT NITROX_AEAD_RCTX(9)

✨ struct nitrox_aead_rctx(9) ✨

okay so this is a page straight out of the Kernel API Manual (section 9, bestie, the kernel interfaces one 💅) and it's all about struct nitrox_aead_rctx — literally the AEAD request context. that's the vibe. it's giving "crypto driver internals" and honestly? iconic.

---

🎀 NAME 🎀

struct nitrox_aead_rctx — the AEAD request context. that's it, that's the whole name. short, sweet, slays.

---

🌸 SYNOPSIS 🌸

here's the whole struct, exactly as it lives, no edits, no notes, just facts:

struct nitrox_aead_rctx {
    struct nitrox_kcrypt_request nkreq;
    unsigned int cryptlen;
    unsigned int assoclen;
    unsigned int srclen;
    unsigned int dstlen;
    u8 *iv;
    int ivsize;
    u32 flags;
    u64 ctx_handle;
    struct scatterlist *src;
    struct scatterlist *dst;
    u8 ctrl_arg;
 };

look at her. twelve members. all accounted for. no cap. 🫶

---

🌈 Members 🌈

let's break down every single field, bestie, because we are not skipping any:

• nkreq — the base request context. like, the foundation the rest sits on. the main character of the struct, honestly.
• cryptlen — the Encryption/Decryption data length. how much actual crypto-able data there is.
• assoclen — the AAD length (that's Additional Authenticated Data, iykyk). it gets authenticated but not encrypted.
• srclen — the input buffer length. how much you're reading from.
• dstlen — the output buffer length. how much room you've got to write into.
• iv — the IV data. a u8 *, pointing right at your initialization vector.
• ivsize — the IV data length. an int, so you know exactly how many bytes of IV you're working with.
• flags — the AEAD request flags. a u32 of pure flag energy.
• ctx_handle — the device context handle, a u64. it's literally the key to your device context. don't lose it 💀
• src — the source sglist (scatterlist pointer). where the data's coming from.
• dst — the destination sglist. where the data's going.
• ctrl_arg — identifies the request type (ENCRYPT/DECRYPT). a u8 that tells you which direction you're going. pick a lane, bestie ✨

---

🦋 SEE ALSO 🦋

if you liked this page (and why wouldn't you), the whole friend group is right here in 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_rfc4106_rctx(9)
• union pkt_instr_hdr(9)
• union pkt_hdr(9)
• union slc_store_info(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)

go read them. seriously. they're all waiting. 🧚💜

---

ngl this page lives in ./drivers/crypto/cavium/nitrox, dated October 2026 — that's the source tree and the date, bestie, noted for the record. 🍓

and that's the whole page!! tysm for reading, go write some AEAD requests, stay hydrated, and remember: the ctx_handle is sacred. mwah 💖🎀🔥👑