crypto_transfer_request(9)

📦 version 7.3.1, in nixpkgs unstable

💅 crypto_transfer_request(9)

Ok so first things first, bestie — this little page lives in the Kernel API Manual, and it's all about one tiny function that has main character energy in the crypto engine world: crypto_transfer_request. She's the one who takes your shiny new request and slides it into the engine queue. Slay. ✨

🦋 NAME

crypto_transfer_request — transfer the new request into the engine queue

Like, that's literally her whole job. No cap. She takes the request and puts it in the queue. Periodt. 💖

🌸 SYNOPSIS

int crypto_transfer_request (struct crypto_engine *engine , struct
       crypto_async_request *req , bool need_pump );

Yes she returns an int, yes she takes three args, and yes you should read the next section before you go touching anything. 🫶

🎀 ARGUMENTS

  • engine — the hardware engine. That's your vibe check target, the actual engine object everything's getting handed over to. 👑
  • req — the request that needs to be listed into the engine queue. She's the new girl and she needs her spot in line. 🌈
  • need_pump — a bool that indicates whether to queue the pump of the request to kthread_work. Basically: do we kick off the pumping or not. That's it, that's the whole flag. ⭐

🔥 SEE ALSO

Bestie, this list is long and honestly iconic. Here's the whole squad:

Like, transfer friends AND finalize friends AND engine lifecycle friends. The whole group chat fr fr. 💜

Ngl, if you're here you probably want the transfer-to-engine variants too — they're all right above, go click around. 💅

And that's the page, bestie! 🧚 It comes from the ./crypto source, dated October 2026, so when you cite her just say crypto_transfer_request(9). Byeee! 🍓🎀

📦 where this page comes from