crypto_trans...st_to_engine(9)

💅 crypto_trans...st_to_engine(9)

okay so bestie, welcome to the Kernel API Manual — yes we're in kernel land today, and yes this one is about crypto_transfer_aead_request_to_engine. It's a whole vibe. Let's get into it 🫶

---

✨ NAME ✨

crypto_transfer_aead_request_to_engine — the function that transfers one aead_request to a list into the engine queue. That's it, that's the whole job. One request. Onto the list. Into the queue. Slay.

---

🌸 SYNOPSIS 🌸

int crypto_transfer_aead_request_to_engine (struct crypto_engine *engine
, struct aead_request *req );

like, it returns an int, it takes an engine, it takes a request, and it goes brrr 🦋

---

🎀 ARGUMENTS 🎀

• engine — the hardware engine, aka the main character doing the actual work 💅
• req — the request that needs to be listed into the engine queue. it wants in. let it in. 🥺

---

👑 SEE ALSO 👑

bestie, there is SO much more where this came from. the whole crew:

• Kernel file ./crypto/crypto_engine.c 🌈
• crypto_finalize_request(9)
• crypto_pump_requests(9)
• crypto_transfer_request(9)
• crypto_transfer_request_to_engine(9)
• crypto_transfer_akcipher_request_to_engine(9)
• crypto_transfer_hash_request_to_engine(9)
• crypto_transfer_kpp_request_to_engine(9)
• crypto_transfer_skcipher_request_to_engine(9)
• crypto_finalize_aead_request(9)
• crypto_finalize_akcipher_request(9)
• crypto_finalize_hash_request(9)
• crypto_finalize_kpp_request(9)
• crypto_finalize_skcipher_request(9)
• crypto_engine_start(9)
• crypto_engine_stop(9)
• crypto_engine_alloc_init_and_set(9)
• crypto_engine_alloc_init(9)
• crypto_engine_exit(9)

literally the entire friend group. iykyk 💖

---

fr fr go read the others too, they're all in ./crypto and they ate 🔥

---

and that's the page!! mwah 💋 this lil guy lives in the ./crypto source, dated October 2026, and it's filed under the very cute truncated name crypto_trans...st_to_engine(9). periodt. ⭐