STRUCT NVMET_FC_PORT_INFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct nvmet_fc_port_info β€” kernel API manual, bestie edition ✨

okay so this page is struct nvmet_fc_port_info(9) and it lives in the Kernel API Manual, and it is literally the little glow-up data element that holds port-specific ids plus FC connection-specific data β€” you use it while you're doing NVME Subsystem role registrations. that's the whole vibe. πŸ’…


🌸 NAME 🌸

struct nvmet_fc_port_info β€” port-specific ids and FC connection-specific data element used during NVME Subsystem role registrations 🫢


πŸŽ€ SYNOPSIS πŸŽ€

she's a struct, she's three fields, she's iconic:

struct nvmet_fc_port_info {
    u64 node_name;
    u64 port_name;
    u32 port_id;
 };

πŸ’– Members πŸ’–

  • node_name β€” the FC WWNN for the port, bestie. that's it, that's the field. ✨
  • port_name β€” the FC WWPN for the port. yes the names are similar, no you may not mix them up. πŸ‘‘
  • port_id β€” the FC N_Port_ID currently assigned to the port. ⚠️ the upper 8 bits must be set to 0 β€” not "should", must. do not test her. πŸ’€

πŸ¦‹ Description πŸ¦‹

Static fields describing the port being registered:

Initialization values for dynamic port fields:

ok so the original really does leave those two lines just sitting there like a vibe check with no follow-up β€” nothing else is spelled out on this page, and I'm not about to invent lore. πŸ™ˆ

🌈 SEE ALSO 🌈

Kernel file ./include/linux/nvme-fc-driver.h β€” go read her, she's the main character πŸ’œ

  • struct nvmefc_ls_req(9)
  • struct nvmefc_ls_rsp(9)
  • struct nvme_fc_port_info(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 nvmefc_tgt_fcp_req(9)
  • struct nvmet_fc_target_port(9)
  • struct nvmet_fc_target_template(9)

and that's the whole page, no cap. this masterpiece ships from ./include/linux, dated October 2026, as part of the Kernel API Manual, and her full title is struct nvmet_fc_port_info(9) β€” mwah, go register some ports responsibly πŸ“πŸ§šπŸ’…

πŸ“¦ where this page comes from