nvme_get_log_discovery(2)

nvme_get_log_discovery 💖

okay bestie, so this one lives in the libnvme API manual, section 2 — it's nvme_get_log_discovery, and it's literally the key to pulling the Discovery log page off your NVMe device. ✨ Put your hair up, grab a matcha, we're going log-diving. 🦋

---

🌸 NAME 🌸

nvme_get_log_discovery — Retrieve Discovery log page 💅

---

✨ SYNOPSIS ✨

int nvme_get_log_discovery (int fd , bool rae , __u32 offset , __u32 len
, void *log );

like… she takes five args and hands you back an int, no cap. 🎀

---

🎀 ARGUMENTS 🎀

• fd — File descriptor of nvme device 🫶 your little handle to the device, the main character of the whole operation.
• rae — Retain asynchronous events ⭐ a bool, so it's giving yes/no energy.
• offset — Offset of this log to retrieve 📍 an __u32, so you're telling her exactly where in the log to start scooping.
• len — The allocated size for this portion of the log 🍓 an __u32 too — how much room you've got for this chunk specifically.
• log — User address to store the discovery log 💖 a void * — this is where the goodies land, so make sure it's actually somewhere valid, bestie, or it's gonna be a bad time 😭.

---

🦋 DESCRIPTION 🦋

Supported only by fabrics discovery controllers, and she returns discovery records. 🌈 That's the whole vibe. If you're not on a fabrics discovery controller, this is not your moment — no notes, just a fact. 🙈

---

🔥 RETURN 🔥

She hands you back The nvme command status if a response was received — check enum nvme_status_field for what those statuses actually mean, iykyk 👑 — or you get -1 with errno set otherwise. 💀 So yeah, negative one = something went sideways, and errno is gonna tell you what.

heads up bestie: that's -1, not "minus one-ish". literally -1. and errno is set. respect the classic. 💅

---

and that's the whole page, babe — this was the libnvme API manual, nvme_get_log_discovery in section 2, dated July 2026. 🎀 slay, go get your discovery records, mwah 🫶💖✨