adf_rl_update_sla(9)

💅 adf_rl_update_sla(9) — the Kernel API Manual, but make it make sense 💅

okay so real talk, bestie: this is the adf_rl_update_sla(9) page from the Kernel API Manual, and it’s giving very specific function energy. No gatekeeping — here’s the whole thing, fr fr.

---

🌸 NAME 🌸

adf_rl_update_sla — handles the update of an SLA.

That’s it. That’s the name vibe. 💖

✨ SYNOPSIS ✨

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

That’s the whole signature, no cap. 🫶

🎀 ARGUMENTS 🎀

• accel_dev — pointer to acceleration device structure.
• sla_in — pointer to user input data required to update an SLA.

Both are pointers, bestie — don’t forget the * energy. ✨

🫶 RETURN 🫶

• 0 — ok.
• -EINVAL — user input data cannot be used to update SLA.

So if you get 0, we cheer; if you get -EINVAL, the input data isn’t usable to update the SLA. Simple as that. 💅

🦋 SEE ALSO 🦋

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

Also go peek at these, 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_get_sla(9), adf_rl_get_capability_remaining(9), adf_rl_remove_sla(9), adf_rl_remove_sla_all(9).

---

mwah 💋 this lil page was brought to you by the source at ./drivers/crypto/intel/qat/qat..., dated October 2026, and it’s all adf_rl_update_sla(9) business. byeee 🫶✨