nvme_mi_adm...associations(2)

💖 nvme_mi_admin_get_log_reachability_associations 💖

okay bestie, so this one is from the libnvme API manual, section 2, and it's literally the plot twist of NVMe-MI: you're grabbing the Reachability Associations Log off a controller. think of it as the controller's "who can even talk to whom rn" gossip page 🫶

---

✨ NAME ✨

nvme_mi_admin_get_log_reachability_associations — Retrieve Reachability Associations Log

no cap, that's the whole vibe: pull the log that tells you which things can reach which things.

---

🎀 SYNOPSIS 🎀

int nvme_mi_admin_get_log_reachability_associations (nvme_mi_ctrl_t ctrl
, bool rao , bool rae , __u32 len , struct
nvme_reachability_associations_log *log );

like... yes, it returns an int. we love a return value. 🧚

---

🌸 ARGUMENTS 🌸

• ctrl — the Controller to query 👑 this is your main character, the one you're interrogating.
• rao — Return associations only 💅 set it and you get just the associations, nothing extra, minimalism era.
• rae — Retain asynchronous events 🦋 because sometimes you want the async events to stay put instead of getting cleared.
• len — the allocated length of the log page 📏 like, how much space you actually set aside. no guessing.
• log — user address to store the log page 🍓 this is where the goods land. you provide the memory, it fills it in.

---

⭐ RETURN ⭐

bestie, here's the tea on what comes back:

The nvme command status if a response was received — peep enum nvme_status_field for the full deets 🔥 — or, and this is the part where we scream, -1 with errno set otherwise 💀

not me reading "or -1 with errno set otherwise" and knowing exactly what kind of day that is. check errno fr fr, it's not gonna tell you on its own. 🙈

---

🌈 and that's the whole page 🌈

lowkey iconic that it's this short. slay, honestly. periodt. 💜

signing off from the libnvme API manual, page nvme_mi_adm...associations(2), dated July 2026 — that's the version and the date, bestie, we keep our receipts 🎀✨