LIBNVME_PATH_GET_NUMA_NODES-LIBNVME3(2)

💅 NAME 💅

libnvme_path_get_numa_nodes — bestie, this is the one that goes and gets your numa_nodes for you ✨

So this little icon lives in the libnvme API manual, section 9, and honestly? She's a vibe. You hand her a path, she hands you back the numa nodes. That's it. That's the whole gig 🫶

---

🦋 SYNOPSIS 🦋

int libnvme_path_get_numa_nodes (const struct libnvme_path *p , const
       char **numa_nodes , const char *dflt );

Like, look at her. Three args, one int coming back. Lowkey elegant ngl 😭

---

🌸 ARGUMENTS 🌸

• p — the struct libnvme_path instance you're querying, aka the main character of this whole operation 👑 She's const, so don't even think about touching her.
• numa_nodes — this is where the value gets stashed when things go right. It's a const char **, so she writes a pointer-to-char into whatever you point her at. Success behavior, periodt ✨
• dflt — the fallback value, and the way this works is so thoughtful honestly: if it fails, this is what ends up sitting in numa_nodes. No empty void, no vibes-based guesswork. Just dflt doing her thing 🎀

---

🔥 RETURN 🔥

• 0 — slay, it worked, success 💖
• -ENOENT — the attribute literally does not exist. She looked. It's not there. F in the chat 💀
• a negative errno — something else went wrong, and the negative errno tells you what 😭

Heads up bestie: those non-success returns are negative errno values, not positive ones. Keep that in mind before you go comparing against ENOENT like a rookie 🙈

---

okay that's the whole page, no cap, every detail accounted for 🧚 If you read this far you're officially a libnvme girlie now, iykyk 💅

libnvme API manual · October 2026 · libnvme_path_get_numa_nodes(9) — mwah, go forth and query those paths bestie 💜🌈⭐