libnvme(2)

✨ NAME ✨

okay so welcome to libnvme(2), the API manual bestie 💖 — and today's main character is struct nvme_fabrics_uri, aka the Parsed URI structure. yep. that's it. that's the whole vibe. a struct that holds a URI that's already been chopped up into cute little pieces for you 🎀

---

🌈 SYNOPSIS 🌈

here's the whole thing, no cap, every field exactly as it lives:

struct nvme_fabrics_uri {
    char *scheme;
    char *protocol;
    char *userinfo;
    char *host;
    int port;
    char **path_segments;
    char *query;
    char *fragment;
 };

like. look at her. she's giving organized. she's giving everything in its lane 💅

---

🦋 Members 🦋

one by one, bestie, so you never mix them up at 2am:

• scheme — the scheme name, and typically it's 'nvme'. that's the whole job. iconic behavior honestly.
• protocol — optional protocol/transport, like 'tcp'. optional!! so don't panic if she's empty.
• userinfo — optional user information component of the URI authority. yes the authority. she's fancy like that 👑
• host — the host transport address. literally where you're going.
• port — the port subcomponent, or 0 if it wasn't specified. zero means "nobody told me", not "port zero", okay?? noted 📝
• path_segments — a NULL-terminated array of path segments. NULL-terminated!! so walk it until you hit NULL and then stop, pls and thank you 🙏
• query — optional query string component, the part separated by '?'. yes, that '?'.
• fragment — optional fragment identifier component, the part separated by '#'. yeah that '#'. the little tail 🌸

lowkey the pattern here: scheme and host are the ones doing the heavy lifting, everything else is optional and just vibing. but you still gotta know all of them, iykyk 💜

---

and that's the page, bestie!! this one came from the libnvme(2) API manual — struct nvme_fabrics_uri — dated July 2026. go parse a URI and slay ✨🫶