lpfc_do_scr_ns_plogi(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– lpfc_do_scr_ns_plogi(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for lpfc_do_scr_ns_plogi(9) β€” yes, the name is a whole mouthful, but we move πŸ’…βœ¨

✨ SYNOPSIS ✨

void lpfc_do_scr_ns_plogi (struct lpfc_hba *phba , struct lpfc_vport
       *vport );

πŸŽ€ ARGUMENTS πŸŽ€

  • phba β€” pointer to lpfc hba data structure.
  • vport β€” pointer to a virtual N_Port data structure.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this routine issues a Port Login (PLOGI) to the Name Server with State Change Request (SCR) for a vport. literally doing the most for that vport, and we love that for it πŸ’–

This routine will create an ndlp for the Name Server associated to the vport if such node does not already exist. no node? bestie, it makes one. periodt.

The PLOGI to Name Server is issued by invoking the lpfc_issue_els_plogi routine. iconic behavior, no cap.

If Fabric-Device Management Interface (FDMI) is configured to the vport, a FDMI node will be created and the PLOGI to FDMI is issued by invoking lpfc_issue_els_plogi routine. so yeah β€” FDMI configured? new FDMI node, same lpfc_issue_els_plogi routine energy πŸ¦‹βœ¨

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/lpfc/lpfc_els.c β€” and the whole squad of related refs:


and that’s the whole vibe 🫢 kisses from ./drivers/scsi/lpfc, dated October 2026 β€” page name still serving lpfc_do_scr_ns_plogi(9) energy πŸ’…βœ¨

πŸ“¦ where this page comes from