lpfc_get_sli4_parameters(9)

📦 version 7.3.1, in nixpkgs unstable

✨ lpfc_get_sli4_parameters — a Kernel API Manual moment ✨

okay so bestie, buckle up, because we're in the Kernel API Manual, section 9, and the star of the show is lpfc_get_sli4_parameters(9) 💅

🌸 NAME 🌸

lpfc_get_sli4_parameters — Get the SLI4 Config PARAMETERS. like, the actual parameters. the SLI4 ones. periodt 🎀

🦋 SYNOPSIS 🦋

int lpfc_get_sli4_parameters (struct lpfc_hba *phba , LPFC_MBOXQ_t
*mboxq );

that's it, that's the whole signature, no cap 🫶

💖 ARGUMENTS 💖

  • phba — Pointer to HBA context object. your whole vibe lives here ✨
  • mboxq — Pointer to the mailboxq memory for the mailbox command response. this is where the answer comes back to you, bestie 📬

🔥 DESCRIPTION 🔥

So this function gets called in the SLI4 code path to read the port's sli4 capabilities. that's the whole job. it's giving "just read the capabilities, ma'am" 👑

It may be called from any context that can block-wait for the completion. so if you can wait, you can call. the expectation is that this routine is called typically from probe_one or from the online routine 🧚

fr fr, remember the block-wait part — that's the actual constraint here, not just lore 💀

🌈 SEE ALSO 🌈

the friend group is HUGE and honestly iconic. Kernel file ./drivers/scsi/lpfc/lpfc_init.c and then all of these 🦋

and that's the whole page bestie, no notes 💜

💫 cute little sign-off: this gem lives in the source ./drivers/scsi/lpfc, and the date on it is October 2026, in the Kernel API Manual, page lpfc_get_sli4_parameters(9). go read it, it ate 💅✨
📦 where this page comes from