nvme_init_g...ility_groups(9)

✨ NAME ✨

nvme_init_get_log_reachability_groups — bestie, this is the one that initializes the passthru command for Retrieve Reachability Groups 💅

(Also, hi, you're reading the libnvme API manual, section 9 — welcome to the cool part of the library 🫶)

---

🌸 SYNOPSIS 🌸

void nvme_init_get_log_reachability_groups (struct libnvme_passthru_cmd
*cmd , bool rgo , struct nvme_reachability_groups_log *log , __u32 len
);

okay so it's a void function — it sets things up and hands them back to you, no return value to stress about, periodt ✨

---

🎀 ARGUMENTS 🎀

• cmd — the passthru command you're gonna use 🔥 like, the buffer you're handing over to get filled in.
• rgo — Return groups only 👑 a bool, so it's a yes/no vibe check.
• log — the user address where the log page gets stored 💖 that's your struct nvme_reachability_groups_log *, ngl she's the main character here.
• len — the allocated length of the log page 🌸 a __u32, so mind your sizing, iykyk.

---

🦋 DESCRIPTION 🦋

So what does it actually do? It initializes the passthru command buffer for the Get Log command, with the LID value set to NVME_LOG_LID_REACHABILITY_GROUPS. That's the whole flex 💀✨

Like — you bring the buffer, it wires up the Get Log bits, and the LID is literal NVME_LOG_LID_REACHABILITY_GROUPS, no cap. Then you go send it. Slay.

---

fr fr, double-check that len matches what you actually allocated before you send anything — the manpage says it's the allocated length of the log page, so treat it with respect 🙈

---

that's the whole page, bestie — go get those reachability groups 💜

sign-off szn 🎀: this was the libnvme API manual, dated October 2026, source line nvme_init_get_log_reachabilit (truncated in the footer, so don't come for me 😭) — mwah, see you in the next manpage 🌈⭐