adf_rl_add_sla(9)

📦 version 7.3.1, in nixpkgs unstable

✨ adf_rl_add_sla(9) — the Kernel API Manual moment 💅

okay so bestie, welcome to the <pink>adf_rl_add_sla</pink> page, section 9 of the Kernel API Manual — yes we're in kernel-land, yes it's giving main character energy 🎀

🌸 NAME 🌸

adf_rl_add_sla — handles the creation of an SLA. that's it, that's the whole vibe. it literally handles the creation of an SLA, no cap 🫶

🦋 SYNOPSIS 🦋

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

like, it takes two pointers and returns an int. simple. iconic. periodt ✨

💖 ARGUMENTS 💖

  • accel_dev — pointer to acceleration device structure. your accel device bestie, she's a struct adf_accel_dev * and you're passing her by pointer, obviously 💫
  • sla_in — pointer to user input data required to add an SLA. all the user input you need to actually add that SLA lives in here, in a struct adf_rl_sla_input_data * 🍓

👑 RETURN 👑

the return value tells you how it went, so pay attention bestie, this is the vibe check 🔥

  • 0 — ok 💚 like everything slayed, we're good
  • -ENOMEM — memory allocation failed 😭 the allocator said no
  • -EINVAL — invalid user input 🙈 you gave it something it can't work with
  • -ENOSPC — all available SLAs are in use 💀 no space left, every SLA is taken, there is literally no room
ngl always check that return value. doesn't matter how cute your pointers are, -ENOSPC will humble you fr fr.

🌈 SEE ALSO 🌈

the whole friend group, in the order the page lists them 🫶

Kernel file ./drivers/crypto/intel/qat/qat_common/adf_rl.c — that's where the code lives, iykyk

go read those too, they're all part of the same little ecosystem, obsessed honestly 🌟

and that's the page!! sourced from ./drivers/crypto/intel/qat/qat..., dated October 2026, page adf_rl_add_sla(9) — mwah, go create some SLAs responsibly 💜🎀

📦 where this page comes from