spum_ns2_ctx_max_payload(9)

💖 spum_ns2_ctx_max_payload(9) — Kernel API Manual, but make it make sense 💖

okay so bestie, welcome to the spum_ns2_ctx_max_payload(9) page from the Kernel API Manual. We're here to determine the max length of the payload for a SPU message for a given cipher and hash alg context. it's giving “small helper, big chunking energy” ✨

🌸 NAME 🌸

spum_ns2_ctx_max_payload — determine the max length of the payload for a SPU message for a given cipher and hash alg context. literally the whole point, and she ate. 💅

🎀 SYNOPSIS 🎀

u32 spum_ns2_ctx_max_payload (enum spu_cipher_alg cipher_alg , enum
spu_cipher_mode cipher_mode , unsigned int blocksize );

🌈 ARGUMENTS 🌈

• cipher_alg — the cipher algorithm. yes bestie, you gotta tell her which one.
• cipher_mode — the cipher mode. mode check, but make it cipher. 💅
• blocksize — the size of a block of data for this algo.

🦋 DESCRIPTION 🦋

Okay so the max payload must be a multiple of blocksize — mandatory, not a suggestion, periodt. Why? Because if a request is too large to fit in a single SPU message, the request can be broken into max_payload sized chunks. Each chunk must also be a multiple of blocksize. So yeah, the chunk math has to math. ✨

👑 RETURN 👑

Max payload length in bytes. that's it, that's the tea. 💖

🔥 SEE ALSO 🔥

Kernel file ./drivers/crypto/bcm/spu.c — go read the source, bestie, iykyk. Also these iconic little functions:

• spum_nsp_ctx_max_payload(9)
• spum_response_hdr_len(9)
• spum_hash_pad_len(9)
• spum_gcm_ccm_pad_len(9)
• spum_assoc_resp_len(9)
• spum_aead_ivlen(9)
• spum_hash_type(9)
• spum_digest_size(9)
• spum_create_request(9)
• spum_cipher_req_init(9)
• spum_cipher_req_finish(9)
• spum_request_pad(9)
• spum_xts_tweak_in_payload(9)
• spum_tx_status_len(9)
• spum_rx_status_len(9)
• spum_status_process(9)
• spum_ccm_update_iv(9)
• spum_wordalign_padlen(9)

okay bye bestie 🫶 — this page is from ./drivers/crypto/bcm, dated October 2026, and it's literally the spum_ns2_ctx_max_payload(9) manual page. mwah 💋✨