nvme_get_an...from_id_ctrl(2)

✨ NAME ✨

nvme_get_ana_log_len_from_id_ctrl — bestie, this one goes and finds you the maximum possible ANA log size 💖

---

🌸 SYNOPSIS 🌸

size_t nvme_get_ana_log_len_from_id_ctrl (const struct nvme_id_ctrl
*id_ctrl , bool rgo );

okay so like, she takes your controller identify data and a lil boolean and she hands you back a size_t, periodt ✨

---

🎀 ARGUMENTS 🎀

• id_ctrl — the Controller identify data, like the whole vibe file for the controller 👑 you already pulled this, don't stress.
• rgo — if this is true, you're asking for the maximum log page size without NSIDs 💅 (yes literally just the maximum, no namespace IDs invited to the function)

---

🦋 RETURN 🦋

She returns a byte limit on the size of the controller's ANA log page ⭐ like that's it, that's the number, that's the limit, no cap 🫶

not me actually loving a function that just does one thing and does it correctly 😭 iconic behavior fr fr

---

that's the whole page, bestie, short and slay 🌈 This little slice of the libnvme API manual said its piece back in July 2026, so if you're reading this way later, mwah, still valid 💜🦋