crypto_engine_alloc_init(9)

💖 NAME 💖

okay so bestie, this is crypto_engine_alloc_init — the Kernel API Manual page for it — and what it does is literally allocate a crypto hardware engine structure and initialize it. like it builds the thing AND sets it up, one stop. slay.

---

✨ SYNOPSIS ✨

struct crypto_engine * crypto_engine_alloc_init (struct device *dev ,
       bool rt );

---

🎀 ARGUMENTS 🎀

• dev — the device attached with one hardware engine. like, the hardware bestie this engine belongs to 🫶
• rt — whether this queue is set to run as a realtime task. true = realtime vibes, false = chill vibes.

---

🌸 DESCRIPTION 🌸

Real talk: this must be called from context that can sleep. no cap, that's the whole rule. do not come at this from an atomic context, it will not end well for you 😭

---

🦋 RETURN 🦋

On success you get the crypto engine structure — iconic, you ate. otherwise you get NULL, and you should probably go think about what happened 💀

---

🌈 SEE ALSO 🌈

Kernel file ./crypto/crypto_engine.c, plus the whole friend group:

• 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_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_exit(9)

---

mwah 💋 this one's from ./crypto, dated October 2026, and it's the crypto_engine_alloc_init(9) page — go build something gorgeous with it. periodt. 🧚✨