nvme_mi_admin_get_nsid_log(2)

💖 NAME 💖

nvme_mi_admin_get_nsid_log — ok bestie, this one's a helper for the Get Log Page functions ✨

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_nsid_log (nvme_mi_ctrl_t ctrl , bool rae , enum
nvme_cmd_get_log_lid lid , __u32 nsid , __u32 len , void *log );

Like. Six arguments. She's thorough, she's got range, she ate 💅

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller you're querying 🫶 that's your main character right there
• rae — Retain Asynchronous Events (yes, literally just that, no further explanation given, iykyk)
• lid — the Log identifier, aka which log we're pulling 👑
• nsid — the Namespace ID 🦋
• len — length of the log buffer, so, how much room we're giving her 📏
• log — pointer for the resulting log data, this is where the goods land 🌈

---

💜 DESCRIPTION 💜

So what she does is: she performs a Get Log Page Admin command, specifically for a log ID lid and a namespace ID nsid ✨

The log data is expected to be len bytes long, and on success it gets stored in log. That's the deal, no cap 💖

And the rae flag? It gets passed as-is straight to the Get Log Page command, periodt. It's specific to the Log Page you requested, so it's not her job to interpret it — she just hands it over 🙈

---

⭐ RETURN ⭐

She gives you the nvme command status if a response was received (peep enum nvme_status_field for the deets), or -1 with errno set otherwise 😭

---

ngl bestie, if you get a -1 back, go check errno — that's where the tea is 🍓

---

k byeeee, this was the libnvme API manual page for nvme_mi_admin_get_nsid_log, section 2 of the manuals, dated July 2026 🎀✨ slay responsibly, go read your logs 💅💖