nvme_init_g...ate_limiting(9)

💅 nvme_init_g...ate_limiting(9)

okay so bestie, welcome to the libnvme API manual — yes that's the manual we're in, and yes this page is short, but it's iconic and we're gonna read it together 🫶

---

✨ NAME ✨

nvme_init_get_log_rate_limiting — the one that initializes the passthru command for Rate Limiting. that's it. that's the whole job. main character energy but make it a log page 🎀

---

🌸 SYNOPSIS 🌸

void nvme_init_get_log_rate_limiting (struct libnvme_passthru_cmd *cmd ,
__u64 lpo , void *log , __u32 len );

like, she takes four things and returns void — no drama, no return value, she just does the thing 💅

---

🦋 ARGUMENTS 🦋

• cmd — the passthru command you're gonna use. this is the one getting set up, so hand her over fr fr ✨
• lpo — offset into the log page. it's a __u64, so like… big offset energy 👑
• log — the log page data buffer. void * because she's flexible like that 🌈
• len — length, in bytes, of the user buffer you're providing to hold the log data. a __u32. count your bytes bestie, she's gonna trust you 🍓

---

💜 DESCRIPTION 💜

so what does she actually do? she initializes the passthru command buffer for the Get Log command, with the LID value NVME_LOG_LID_RATE_LIMITING. that's the vibe check: Get Log + that specific LID, all set up and ready 💖

no cap, no extra steps, no secret sauce — that's the whole description and she ate 🔥

---

lowkey the most important thing here is that LID constant: NVME_LOG_LID_RATE_LIMITING. if you're not passing that vibe, you're on a different log page entirely, iykyk 🙈

---

and that's the page!! this little cutie comes from the libnvme API manual, dated October 2026 — mwah, go initialize some rate limiting logs, you got this 🧚⭐💅