libnvme(9)

🌸 NAME 🌸

struct nvme_exported_port_delete_data — the Manage Exported Port Delete Data Structure, aka the little payload you hand over when you're like "bestie, this exported port? gone. bye." 💅

This is a page from the libnvme(9) API Manual, so yeah, it's kernel-adjacent vibes but make it cute.

✨ SYNOPSIS ✨

struct nvme_exported_port_delete_data {
    __u8 subnqn[256];
    __le16 epid;
    __u8 rsvd258[62];
 };

That's the whole struct, no cap. Three members, one of them is just reserved padding doing absolutely nothing (we respect the hustle tho 🫶).

🎀 Members 🎀

• subnqn — the Exported NVM Subsystem NQN (SUBNQN) that goes with the Exported Port you're deleting. It's a __u8 array of 256 bytes, so lowkey a whole personality's worth of name space. 🔥
• epid — the Exported Port ID (EPID) of the Exported Port you want to delete. It's a __le16 (little-endian, bestie, please respect the byte order 🙈), so it's the specific port, identified, targeted, done. ⭐
• rsvd258 — Reserved. That's it. That's the member. __u8 rsvd258[62] of pure reserved energy, just holding space so everything lands where the spec says it should. Not me defending a 62-byte vibe check 💀

Real talk: rsvd258 is reserved — don't go stuffing your own data in there hoping nobody notices. Reserved means reserved, fr fr. ✨

🦋 A lil sign-off 🦋

This page lives in the libnvme(9) manual — printed up in October 2026 — and it's all about struct nvme_exported_port_delete_data, which honestly deserves its own main character energy for how tidy it is. Go forth and delete those exported ports, bestie. 🌈👑🎀