adf_rl_get_sla(9)

💅 adf_rl_get_sla — the NAME section, bestie

okay so adf_rl_get_sla — literally just returns an existing SLA data. that's the whole vibe. this is from the Kernel API Manual (adf_rl_get_sla(9)), and yes we're gonna get into it 💖

---

✨ SYNOPSIS ✨

int adf_rl_get_sla (struct adf_accel_dev *accel_dev , struct
       adf_rl_sla_input_data *sla_in );

that's it. two args, one int coming back at you. slay 🫶

---

🎀 ARGUMENTS 🎀

• accel_dev — pointer to the acceleration device structure. like, the device itself, the main character 👑
• sla_in — pointer to user data where the SLA info will be stored. this is where the good stuff lands, no cap 🍓

---

🌸 DESCRIPTION 🌸

okay so here's the thing: the sla_id you want data for? you gotta set it in the sla_id structure first. that's the whole entry requirement. set the sla_id, then ask. iykyk ✨

---

💀 RETURN 💀

• 0 — ok 💚 everything's fine, we ate
• -EINVAL — provided sla_id does not exist 😭 like it's just not there bestie, invalid, gone, not a real one

---

🦋 SEE ALSO 🦋

Kernel file ./drivers/crypto/intel/qat/qat_common/adf_rl.c

and the whole friend group, fr fr:

• 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_sla_id(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_capability_remaining(9)
• adf_rl_remove_sla(9)
• adf_rl_remove_sla_all(9)

like, the entire roster. obsessed 🌈

---

ngl, quick vibe check: adf_rl_get_sla(9) only reads — it's the get, not the add or the remove. the removing ones are right there in SEE ALSO if you're feeling chaotic 💅

---

that's the page, bestie 🧚 source/version lives at ./drivers/crypto/intel/qat/qat... and it's dated October 2026 — mwah, bye 💜