lpfc_unreg_vpi(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

lpfc_unreg_vpi(9) β€” okay bestie, this one is literally β€œPrepare a mailbox command for unregistering vport id.” And yes, we’re in the Kernel API Manual now, so grab your iced coffee and let’s get into it πŸ’…


✨ SYNOPSIS ✨

void lpfc_unreg_vpi (struct lpfc_hba *phba , uint16_t vpi , LPFC_MBOXQ_t *pmb );

Return type is void, so no return value is coming back to you β€” it’s giving β€œdo the prep, no receipts” energy 🫢


πŸ’… ARGUMENTS πŸ’…

  • phba β€” pointer to lpfc hba data structure. Yep, the hba said β€œthat’s me.”
  • vpi β€” virtual N_Port identifier. This is the vport-id bestie in question πŸ¦‹
  • pmb β€” pointer to the driver internal queue element for mailbox command. It’s the little mailbox vessel that carries the command πŸ’Œ

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so the unregistration vport identifier mailbox command is used to inactivate a virtual N_Port. That’s the whole vibe: this command makes that virtual N_Port go inactive.

⚠️ Important caveat, no cap: the driver must have logged out and unregistered all remote N_Ports to abort any activity on the virtual N_Port. So handle that first, bestie. Don’t skip the prerequisites.

The HBA will unregister any default RPIs associated with the specified vpi, aborting any active exchanges. It will also post the mailbox response after making the virtual N_Port inactive. So the HBA does its thing, then reports back β€” iconic behavior honestly πŸ‘‘

This routine prepares the mailbox command for unregistering a virtual N_Port. It’s the setup step, the β€œget the mailbox ready” moment, the pre-game if you will ✨


🌸 SEE ALSO 🌸

Kernel file: ./drivers/scsi/lpfc/lpfc_mbox.c β€” home of the mailbox lore 🧚


Signing off with source/version ./drivers/scsi/lpfc, date October 2026, and page lpfc_unreg_vpi(9) energy β€” slay, bestie, go prepare that mailbox command πŸ’–πŸŽ€βœ¨

πŸ“¦ where this page comes from