lpfc_issue_els_scr(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_issue_els_scr — like, the ELS SCR manual, bestie

okay so this is the kernel API page for lpfc_issue_els_scr(9), which lives in the lpfc driver and is about issuing a scr to an node on a vport (yes, "an node", the original said it, I'm not fixing it, it's iconic 🎀).

✨ NAME ✨

lpfc_issue_els_scr — Issue a scr to an node on a vport 🦋

🌸 SYNOPSIS 🌸

int lpfc_issue_els_scr (struct lpfc_vport *vport , uint8_t retry );

like literally that's the whole signature, no cap 💅

🎀 ARGUMENTS 🎀

  • vport — pointer to a host virtual N_Port data structure. so like, the vport in question 🫶
  • retry — the retry counter for the command IOCB. it's a uint8_t, keep it cute ✨

💖 DESCRIPTION 💖

okay so bestie, listen up. This routine issues a State Change Request (SCR) to a fabric node on a vport. no biggie. The remote node is the Fabric Controller (0xfffffd) — main character energy honestly 👑.

The way it works: it first searches the vport node list to find the matching ndlp. If no such ndlp is found, a new ndlp shall be created for this (SCR) purpose. 😭 Then an IOCB is allocated, payload prepared, and the lpfc_sli_issue_iocb routine is invoked to send the SCR IOCB. slay.

bestie note: the ndlp reference count will be incremented by 1 for holding the ndlp, and the reference to ndlp will be stored into the ndlp field of the IOCB for the completion callback function to the SCR ELS command. don't forget that or it's giving memory leak 💀

And the return codes, fr fr:

  • 0 — Successfully issued scr command ✅
  • 1 — Failed to issue scr command 🔥

🦋 SEE ALSO 🦋

Kernel file ./drivers/scsi/lpfc/lpfc_els.c — and honestly, the whole friend group:

🌈 and that's the whole page, bestie! this lil beauty comes from the source tree ./drivers/scsi/lpfc, dated October 2026, and it's filed under the manual page lpfc_issue_els_scr(9). go read your kernel source, iykyk 💜🫶🍓

kind of obsessed with how this whole thing is one function and 100 SEE ALSOs tbh 💀

📦 where this page comes from