can_node_afford_update(9)

💖 can_node_afford_update(9) — Kernel API Manual 💖

okay so bestie, welcome to the can_node_afford_update(9) page from the Kernel API Manual ✨ this one is lowkey the vibe-check bouncer for SLA updates, and it's about to make so much sense.

---

🌸 NAME 🌸

can_node_afford_update — Verifies if SLA can be updated with input data 🫶

---

✨ SYNOPSIS ✨

bool can_node_afford_update (struct adf_rl_sla_input_data *sla_in ,
       struct rl_sla *sla );

---

🎀 ARGUMENTS 🎀

• sla_in — pointer to user input data for a new SLA 💌
• sla — pointer to SLA object selected for update 👑

---

🦋 DESCRIPTION 🦋

The algorithm is doing a whole vibe check, no cap: it verifies if a new CIR value is big enough to satisfy currently assigned child SLAs, and it checks if PIR can be updated 💅

That's the whole glow-up. Very demure, very mindful, very SLA-update-core 🌸

---

👑 RETURN 👑

• true — SLA can be updated ✅
• false — SLA cannot be updated ❌

---

🌈 SEE ALSO 🌈

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)
• 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_sla(9)
• adf_rl_get_capability_remaining(9)
• adf_rl_remove_sla(9)
• adf_rl_remove_sla_all(9) ✨

---

source/version ./drivers/crypto/intel/qat/qat... 💌 date October 2026 🎀 can_node_afford_update(9) signing off, mwah 💋✨