sec_queue_alloc_start_safe(9)

💅 sec_queue_alloc_start_safe(9) — like, the whole glow-up

okay bestie, so we're in the Kernel API Manual, section 9, and the star of the show is sec_queue_alloc_start_safe 🎀 — yes that's the actual page name, and yes it's a whole vibe. It grabs you a hardware queue from whichever instance it feels like. Let's get into it ✨

---

🌸 NAME 🌸

sec_queue_alloc_start_safe — get a hw queue from appropriate instance 🦋

---

✨ SYNOPSIS ✨

struct sec_queue * sec_queue_alloc_start_safe (void );

Like, that's it. That's the whole call. She takes nothing and she gives you a struct sec_queue *. Iconic behaviour honestly 👑

---

🎀 ARGUMENTS 🎀

• void — no arguments, bestie. Zero. None. Nada. She doesn't want your input, she just wants to hand you a queue 💅

---

🔥 DESCRIPTION 🔥

So here's the tea: this function does extremely simplistic load balancing. Like, extremely. We're talking "whatever, here's a queue" energy, not a carefully curated matchmaking service 😭

It does not take into account:

• the NUMA locality of the accelerator 🫶
• which cpu has requested the queue 💀

ngl, that's kind of a lot to just... not consider. But that's where we're at.

The page does say that future work may focus on optimizing this in order to improve full machine throughput — so like, she's aware of her flaws, she's growing, we respect the journey 🌈⭐

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/crypto/hisilicon/sec/sec_drv.c — go read the source, iykyk 📖
• sec_queue_stop_release(9)
• sec_queue_empty(9)
• sec_queue_send(9)

Like, the whole queue friend group honestly 🫶 go say hi to all of them.

---

and that's the page!! mwah 💖 this one lives over in ./drivers/crypto/hisilicon/sec, and it was stamped October 2026 — so go forth, allocate your queue safely, and slay the day, bestie 💅✨👑