spu_aead_tx_sg_create(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to spu_aead_tx_sg_create(9) from the Kernel API Manual β€” it’s giving kernel-crypto scatterlist realness, and we’re gonna get through every detail together πŸ’…βœ¨

πŸ’– NAME πŸ’–

spu_aead_tx_sg_create β€” build up the scatterlist of buffers used to send a SPU request message for an AEAD request. Includes SPU message headers and the request data. πŸŽ€

🌸 SYNOPSIS 🌸

the whole signature, untouched, because bestie we do not mess with function signatures 😀

int spu_aead_tx_sg_create (struct brcm_message *mssg , struct
iproc_reqctx_s *rctx , u8 tx_frag_num , u32 spu_hdr_len , struct
scatterlist *assoc , unsigned int assoc_len , int assoc_nents , unsigned
int aead_iv_len , unsigned int chunksize , u32 aad_pad_len , u32 pad_len
, bool incl_icv );

πŸŽ€ ARGUMENTS πŸŽ€

every single one, no skipping, periodt:

  • mssg β€” the mailbox message containing the transmit sg.
  • rctx β€” the crypto request context.
  • tx_frag_num β€” number of scatterlist elements required to construct the SPU request message.
  • spu_hdr_len β€” length of SPU message header in bytes.
  • assoc β€” crypto API associated data scatterlist.
  • assoc_len β€” length of associated data.
  • assoc_nents β€” number of scatterlist entries containing assoc data.
  • aead_iv_len β€” length of AEAD IV, if included.
  • chunksize β€” Number of bytes of request data.
  • aad_pad_len β€” Number of bytes of padding at end of AAD. For GCM/CCM.
  • pad_len β€” Number of pad bytes.
  • incl_icv β€” If true, write separate ICV buffer after data and any padding.

πŸ¦‹ DESCRIPTION πŸ¦‹

so the scatterlist that gets allocated here? it gets freed in spu_chunk_cleanup when the request completes, whether the request is handled successfully or there is an error. no cap, cleanup covers both the slay and the oops πŸ’€βœ¨

⭐ RETURN ⭐

0 if successful, < 0 if an error.

🫢 SEE ALSO 🫢

Kernel file ./drivers/crypto/bcm/cipher.c is the main-character source path, and here are all the (9) buddies:


that’s the whole page, bestie β€” source/version path ./drivers/crypto/bcm, date October 2026, mwah πŸ’‹πŸŽ€πŸ«Ά

πŸ“¦ where this page comes from