LIBNVME_TRANSPORT_IS_FABRIC-LIBNVME3(2)

πŸ“¦ version 3.2, in arch rolling

πŸ’… libnvme_transport_is_fabric

okay so bestie, welcome to the libnvme API manual ✨ β€” yes we're doing C documentation today, and yes it's gonna be cute. this one's a little function with big "is it or isn't it" energy, so let's get into it πŸŽ€


🌸 NAME 🌸

libnvme_transport_is_fabric β€” the vibe check that tells you if a transport string is a fabrics one. literally returns true for a fabrics transport string, iykyk πŸ¦‹


✨ SYNOPSIS ✨

bool libnvme_transport_is_fabric (const char *transport );

one function, one argument, one bool coming back at you. iconic. πŸ’…


🫢 ARGUMENTS 🫢

  • transport β€” the transport name you're asking about, like "tcp" or "pcie". just a lil string, no cap πŸ“

πŸ”₯ DESCRIPTION πŸ”₯

so every transport is either local or NVMe-over-Fabrics, and that's just the law bestie 🌈

  • local: pcie, apple-nvme
  • NVMe-over-Fabrics: tcp, rdma, fc, loop

use this function when the only thing you've got is the transport string itself 😭 β€” like, you don't have a controller yet to exist and be asked, so you can't go ask libnvme_ctrl_is_transport_fabric instead. this is the lowkey pre-controller option, and honestly? she ate. πŸ‘‘


⭐ RETURN ⭐

  • true if transport is a fabrics transport πŸ’–
  • false if it's local πŸ«₯

that's it, that's the whole answer. no edge cases hiding in the group chat. periodt. πŸ’€


sign-off bestie!! 🧚 this masterpiece dropped in October 2026, straight from the libnvme girliesss β€” go forth and vibe check those transport strings πŸ’œπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from