add_update_sla(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… add_update_sla(9) β€” a Kernel API Manual moment πŸŽ€

okay so bestie, welcome to the add_update_sla(9) page, it's giving kernel API manual energy and honestly we're obsessed. this is the doc for add_update_sla, and it's lowkey the whole vibe for how an SLA gets born and how it gets updated. two jobs, one function, main character energy fr fr. ✨


🌸 NAME 🌸

add_update_sla β€” handles the creation and the update of an SLA πŸ’–


✨ SYNOPSIS ✨

int add_update_sla (struct adf_accel_dev *accel_dev , struct
       adf_rl_sla_input_data *sla_in , bool is_update );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • accel_dev β€” pointer to acceleration device structure, like the actual hardware baddie we're talking to πŸ”₯
  • sla_in β€” pointer to user input data for a new/updated SLA, aka the lore the user is handing over πŸ’…
  • is_update β€” flag to indicate if this is an update or an add operation πŸŽ€ (yes bestie, it's literally the "new or improved" toggle)

πŸ‘‘ RETURN πŸ‘‘

the return values, no cap, every single one:

  • 0 β€” ok 🌈 (slay)
  • -ENOMEM β€” memory allocation failed 😭 (the malloc said no)
  • -EINVAL β€” user input data cannot be used to create SLA πŸ™ˆ (the vibes were off)
  • -ENOSPC β€” all available SLAs are in use πŸ’€ (full, no room, periodt)
fr fr check these before you assume anything worked, bestie. 0 is the only "we ate" answer.

πŸ” SEE ALSO πŸ”

Kernel file ./drivers/crypto/intel/qat/qat_common/adf_rl.c β€” like the whole source right there, iykyk 🧚

and the whole friend group, all of them, in order:


πŸ’– cute little sign-off: this page lives at ./drivers/crypto/intel/qat/qat... and it's dated October 2026 β€” and the manual is add_update_sla(9), which we already knew but like, closure. bye bestie, go read some source 🫢⭐
πŸ“¦ where this page comes from