crypto_trans...st_to_engine(9)

💖 crypto_trans...st_to_engine(9) — Kernel API Manual 💖

okay so bestie, this is the Kernel API Manual page for crypto_trans...st_to_engine(9) — yes, that’s the abbreviated title, and the actual function in the NAME section is crypto_transfer_skcipher_request_to_engine. it’s literally about moving one skcipher_request into the engine queue. short page, main character energy, let’s go 🦋

✨ NAME ✨

crypto_transfer_skcipher_request_to_engine — transfer one skcipher_request to list into the engine queue 💅

🌸 SYNOPSIS 🌸

       int crypto_transfer_skcipher_request_to_engine (struct crypto_engine
       *engine , struct skcipher_request *req );

that’s the whole signature, bestie — no cap 🎀

🧡 ARGUMENTS 🧡

• engine — the hardware engine 👑. that’s the big one.
• req — the request that needs to be listed into the engine queue. yes, into the queue it goes, periodt ✨

🌈 SEE ALSO 🌈

the kernel file is ./crypto/crypto_engine.c — go look, iykyk 🔥

• 💫 crypto_finalize_request(9)
• 💫 crypto_pump_requests(9)
• 💫 crypto_transfer_request(9)
• 💫 crypto_transfer_request_to_engine(9)
• 💫 crypto_transfer_aead_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_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)

mwah 💋 — this page’s source/version is ./crypto, dated October 2026, and it’s the crypto_trans...st_to_engine(9) page. ok bye bestie, slay your queue 🎀👑💖