nvme_mi_adm...og_discovery(2)

✨ NAME ✨

nvme_mi_admin_get_log_discovery — bestie, this one goes and fetches the Discovery log page for u 💅

(yeah it's a libnvme API manual situation, we're in the nvme_mi_admin_... family, iykyk)

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_discovery (nvme_mi_ctrl_t ctrl , bool rae ,
       __u32 offset , __u32 len , void *log );

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller u wanna query, literally the whole point 🫶
• rae — Retain asynchronous events, okay so this is the bool that says whether u keep those async events around or not ✨
• offset — Offset of this log to retrieve, like where in the log u start grabbing from 📍
• len — The allocated size for this portion of the log, so how much room u set aside for this chunk 🧚
• log — User address to store the discovery log, i.e. where the goodies get dropped off 💖

---

🦋 DESCRIPTION 🦋

Supported only by fabrics discovery controllers, no cap — it's giving niche but iconic 👑

And what do u get back? Discovery records. that's the vibe. 🌈

---

👑 RETURN 👑

The nvme command status if a response was received — peep enum nvme_status_field for what those statuses mean, fr fr 📖

Or, if things went sideways, -1 with errno set otherwise 😭💀

not me having to remind u that -1 + errno is the "something went wrong bestie" combo 🙈

---

okay that's the whole page, slay 💅 this was pulled from the libnvme API manual (July 2026 edition, and yes we're obsessed with her) — go forth and retrieve those discovery records, main character 🌟💜