STRUCT NVME_FC_PORT_INFO(9)

✨ struct nvme_fc_port_info(9) ✨

okay bestie, welcome to the Kernel API Manual 🎀 — this one's all about struct nvme_fc_port_info, aka the little bundle of port-specific ids + FC connection-specific data that gets used during NVME Host role registrations. it's giving "backstage pass for your fibre channel port" 💅

---

🦋 SYNOPSIS 🦋

struct nvme_fc_port_info {
    u64 node_name;
    u64 port_name;
    u32 port_role;
    u32 port_id;
    u32 dev_loss_tmo;
 };

---

🌸 Members 🌸

• node_name — the FC WWNN for the port, no cap 🫶
• port_name — the FC WWPN for the port, iconic behavior honestly
• port_role — tells you which NVME roles are supported (peep FC_PORT_ROLE_xxx, iykyk)
• port_id — the FC N_Port_ID that's currently assigned to the port. ⚠️ heads up: the upper 8 bits must be set to 0 — like, non-negotiable, fr fr
• dev_loss_tmo — the maximum delay for reconnects to an association on this device. it's used only on a remoteport, so don't come for it anywhere else 🙈

---

💖 Description 💖

Static fields describing the port being registered:

Initialization values for dynamic port fields:

(yes bestie, that's genuinely how it's laid out — those two little intro lines are sitting there all mysterious and main-character-energy 👑)

---

🔥 SEE ALSO 🔥

Kernel file ./include/linux/nvme-fc-driver.h plus this whole friend group of structs:

• struct nvmefc_ls_req(9)
• struct nvmefc_ls_rsp(9)
• struct nvmefc_fcp_req(9)
• struct nvme_fc_local_port(9)
• struct nvme_fc_remote_port(9)
• struct nvme_fc_port_template(9)
• struct nvmet_fc_port_info(9)
• struct nvmefc_tgt_fcp_req(9)
• struct nvmet_fc_target_port(9)
• struct nvmet_fc_target_template(9)

---

that's the whole page, bestie — go forth and register those ports 💅✨

🦋 sourced from ./include/linux, dated October 2026, and wrapped up in struct nvme_fc_port_info(9) realness — mwah, love u, bye 💜🎀