STRUCT SE_CRYPTO_REQUEST(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct se_crypto_request(9) β€” kernel API manual, bestie edition

okay so picture this: you're deep in the kernel API manual (that's the manual name, iykyk) and you bump into struct se_crypto_request. She's the SE crypto request structure, and honestly? main character energy. Let's get into it πŸŽ€


✨ NAME ✨

struct se_crypto_request β€” the SE crypto request structure. that's her. that's the whole vibe. πŸ’–


🌸 SYNOPSIS 🌸

here's the whole glow-up, verbatim, don't touch a single character:

struct se_crypto_request {
    u8 opcode;
    gfp_t gfp;
    u32 flags;
    u64 ctx_handle;
    struct gphdr gph;
    union se_req_ctrl ctrl;
    u64 *orh;
    u64 *comp;
    struct scatterlist *src;
    struct scatterlist *dst;
 };

like. look at her. iconic. 🫢


πŸ¦‹ Members πŸ¦‹

time for the member-by-member vibe check, no cap:

  • opcode β€” the request opcode (enc/dec). she's either encrypting or decrypting, pick a lane bestie ✨
  • flags β€” flags from the crypto subsystem. the little stickers on the outside of the notebook, fr.
  • ctx_handle β€” the crypto context handle. your VIP pass to the context πŸ’…
  • gph β€” GP Header.
  • ctrl β€” Request Information. yes that's the whole description, and yes it's giving mysterious 🌈
  • orh β€” ORH address.
  • comp β€” completion address. where we all meet up when we're done πŸŽ€
  • src β€” the input sglist. what goes in πŸ“
  • dst β€” the output sglist. what comes out ⭐
quick note bestie: gfp is absolutely sitting up there in the struct being all gfp_t gfp; and living her life, but the Members list does not say anything about her. so we're not gonna make anything up. we simply respect her privacy πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group, and they're all linked from the kernel file ./drivers/crypto/cavium/nitrox/nitrox_req.h:

  • struct gphdr(9)
  • union se_req_ctrl(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)
  • 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 too, they're all serving πŸ”₯


signing off with the receipts: this page lives in ./drivers/crypto/cavium/nitrox and it's stamped October 2026 β€” so yeah, she's from the future, and she ate. periodt. πŸ’œπŸ§š

πŸ“¦ where this page comes from