nvme_set_fe..._arbitration(2)

✨ nvme_set_features_arbitration 💅

okay bestie, welcome to the libnvme API manual 🎀 — also known as nvme_set_fe..._arbitration(2) if you're being all formal about it. pull up a chair, we're gonna talk about arbitration. no cap, it's more fun than it sounds. 🦋

---

🌸 NAME 🌸

nvme_set_features_arbitration — Set arbitration features. yes queen, that's literally it. it sets the arbitration features. we love a self-explanatory name. 👑

---

✨ SYNOPSIS ✨

int nvme_set_features_arbitration (int fd , __u8 ab , __u8 lpw , __u8
mpw , __u8 hpw , bool save , __u32 *result );

that's the whole vibe right there. seven things go in, one int comes out. 🫶

---

🧚 ARGUMENTS 🧚

here's the cast of characters, no skips, no cuts, all of them get their moment:

• fd — File descriptor of nvme device. this is your main character, the handle to the device you're talking to. 🔥
• ab — Arbitration Burst. yes, "ab" really does stand for that, keep up. 💫
• lpw — Low Priority Weight. the low-priority girlies get a say too. 🍓
• mpw — Medium Priority Weight. the middle children. they're valid. 🌈
• hpw — High Priority Weight. the VIPs. main character energy fr fr. 👑
• save — Save value across power states. it's a bool, so it's giving simple: keep it or don't. 💜
• result — The command completion result from CQE dword0. a pointer, because the answer gets handed back to you, not just shouted into the void. ✨

---

💖 RETURN 💖

The nvme command status if a response was received (see enum nvme_status_field) or -1 with errno set otherwise.

so basically: you get a status back when the device answers you, and you get -1 plus an errno when it doesn't. either way you're gonna know what happened. no ambiguity, no mystery, we love clarity. 😭💅

---

heads up bestie: the errno-set path means you should actually check it. don't just peek at the return value and move on, that's not the energy we're bringing. check. your. errors. periodt. 🫶

---

and that's the whole page, literally all of it, nothing skipped. 🦋✨

mwah, this page came from the libnvme API manual — sourced and dated July 2026 (the manpage even abbreviated it to nvme_set_features_arbitranvme_set_fe..._arbitration(2) on its way out, which is honestly iconic of it). 💅💖 bye bestie, go set some arbitration features responsibly! 🎀🌸