acomp_request_set_params(9)

📦 version 7.3.1, in nixpkgs unstable

💅 acomp_request_set_params — Kernel API Manual energy, bestie

Okay so real talk, this is acomp_request_set_params(9) — a function from the Kernel API Manual — and it does exactly one (1) thing: it "Sets request parameters". That's the whole vibe. Iconic, minimal, no notes. 🎀

✨ SYNOPSIS ✨

void acomp_request_set_params (struct acomp_req *req , struct
scatterlist *src , struct scatterlist *dst , unsigned int slen ,
unsigned int dlen );

Like, it returns void. Nothing back. No "did it work", no error code, just vibes and side effects. 🫶

🌸 ARGUMENTS 🌸

  • req — the asynchronous compress request. Your main character, fr. ✨
  • src — pointer to the input buffer scatterlist. i.e. where the data you wanna squeeze is hanging out.
  • dst — pointer to the output buffer scatterlist. Huge caveat though: if this is NULL, the acomp layer will allocate the output memory for you. So it's not "no output", it's "you handle it, bestie". 🫡
  • slen — size of the input buffer. Yes, unsigned int. Yes, counts matter. 💅
  • dlen — size of the output buffer. And here's the cute little plot twist: if dst is NULL, this can be used by the user to specify the maximum amount of memory to allocate. So like, dlen doubles as a budget when you're not providing your own destination. Budget responsibly. 🍓

🌈 DESCRIPTION 🌈

Sets parameters required by an acomp operation. That's it. That's the whole description. Short, sweet, and honestly? She ate. 🔥

Ngl this page is very concise — the description is literally one sentence long, so don't come at me expecting lore. The details live in the arguments up there. 👆

🦋 SEE ALSO 🦋

Kernel file ./include/crypto/acompress.h, plus a whole friend group of related symbols:

And that's a wrap, bestie 🧚 — this page ships from ./include/crypto in the October 2026 release of the Kernel API Manual. Go set those params, slay, and remember: dst = NULL means the acomp layer's got your back. 💖✨

📦 where this page comes from