get_next_free_sla_id(9)

💅 get_next_free_sla_id(9) — the Kernel API Manual glow-up

okay bestie, gather round, because this little function from the Kernel API Manual is about to be your new fave. It's called get_next_free_sla_id, and its whole entire job is literally finding the next free ID in the SLA array. That's it. That's the vibe. ✨

---

🎀 NAME 🎀

get_next_free_sla_id — finds next free ID in the SLA array. no cap, that's the whole thing 🫶

---

🌸 SYNOPSIS 🌸

int get_next_free_sla_id (struct adf_rl *rl_data );

---

🦋 ARGUMENTS 🦋

• rl_data — Pointer to ratelimiting data structure. that's your one (1) input, bestie, a pointer to the ratelimiting data struct. iconic. 💅

---

✨ RETURN ✨

the return value is giving "two possible timelines" energy:

• 0 : RL_NODES_CNT_MAX — correct ID 🎉 (like, you got a valid one, slay)
• -ENOSPC — all SLA slots are in use 😭 (every slot is taken, no room, the array said "we're full")

---

💜 SEE ALSO 💜

so here's the friend group, fr fr:

• Kernel file ./drivers/crypto/intel/qat/qat_common/adf_rl.c
• find_parent(9)
• adf_rl_get_sla_arr_of_type(9)
• prepare_rp_ids(9)
• can_parent_afford_sla(9)
• can_node_afford_update(9)
• get_next_free_node_id(9)
• add_new_sla_entry(9)
• add_update_sla(9)
• adf_rl_add_sla(9)
• adf_rl_update_sla(9)
• adf_rl_get_sla(9)
• adf_rl_get_capability_remaining(9)
• adf_rl_remove_sla(9)
• adf_rl_remove_sla_all(9)

---

💀 reminder bestie: if you get -ENOSPC back, that's not a you problem, the SLA slots are genuinely all in use. don't go inventing IDs, iykyk.

---

and that's the whole page! 🧚 mwah. source/version is ./drivers/crypto/intel/qat/qat..., dated October 2026, and this little slice of get_next_free_sla_id(9) excellence is officially wrapped. go forth and find those free IDs, main character 💖🌈⭐