nvme_parse_uri(2)

💖 nvme_parse_uri — bestie's guide to the libnvme API 💖

okay so you found yourself in the libnvme API manual, section 2, staring at nvme_parse_uri and wondering what it wants from you. don't panic, we're gonna get through this together 🫶

---

✨ NAME ✨

nvme_parse_uri — literally just, parse the URI string 💅

no cap, that's the whole job.

---

🦋 SYNOPSIS 🦋

struct nvme_fabrics_uri * nvme_parse_uri (const char *str );

that's the vibe, that's the whole signature ✨

---

🌸 ARGUMENTS 🌸

• str — the URI string. that's it, that's the babygirl. she's a const char * and she's carrying your whole URI 🎀

---

👑 DESCRIPTION 👑

so like, this function takes that URI string and parses it — as defined in the NVM Express Boot Specification, so bestie this isn't freestyle, there's a spec and we respect her 📜

the supported URI elements look like this, periodt:

nvme+tcp://userhost:port/subsys_nqn/nid?query=val#fragment

look at her go 💅 that's user, host, port, subsys_nqn, nid, query, and fragment all living in one little string. iconic behaviour, honestly.

---

⭐ RETURN ⭐

• you get an nvme_fabrics_uri structure back on success — slay 🎉
• you get NULL on failure, and with errno set — so please, for the love of everything, check your errno 🙈

---

🌈 SEE ALSO 🌈

(no SEE ALSO section in the original, bestie — this page is a solo act 👑)

---

that's the whole page fr fr. now go parse something cute 💜

---

signing off from the libnvme API manual, section 2, nvme_parse_uri — dated July 2026. mwah, go forth and parse responsibly 🧚✨