lpfc_nvmet_xmt_fcp_op_cmp(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_nvmet_xmt_fcp_op_cmp(9) 💅

okay bestie, welcome to the Kernel API Manual entry for lpfc_nvmet_xmt_fcp_op_cmp(9) — yes that's a whole mouthful, yes it's iconic, no we're not shortening it. buckle up 🎀

✨ NAME ✨

lpfc_nvmet_xmt_fcp_op_cmp — Completion handler for FCP Response 💖

🌸 SYNOPSIS 🌸

void lpfc_nvmet_xmt_fcp_op_cmp (struct lpfc_hba *phba , struct
lpfc_iocbq *cmdwqe , struct lpfc_iocbq *rspwqe );

like, that's the whole signature. short king. 👑

🦋 ARGUMENTS 🦋

  • phba — Pointer to HBA context object. that's your HBA bestie, the main character of this whole operation ✨
  • cmdwqe — Pointer to driver command WQE object. the WQE that's out here doing the commanding 🫡
  • rspwqe — Pointer to driver response WQE object. and this one's the response WQE, showing up to reply, as it should 💅

🧚 DESCRIPTION 🧚

okay so here's the tea 🍓 — this function gets called from the SLI ring event handler with no lock held. no cap, zero locks. it's giving "we trust you, go off" energy.

This function is the completion handler for NVME FCP commands. and what does it actually do? it frees memory resources used for the NVME commands. that's the whole vibe check: clean up, give the memory back, slay, move on. 🔥

🌈 SEE ALSO 🌈

first up, the kernel file this lives in:

  • Kernel file ./drivers/scsi/lpfc/lpfc_nvmet.c

and the whole friend group of related functions — literally all of them, no gatekeeping:

and that's the page, bestie 🫶 this lil chapter of the Kernel API Manual lives at ./drivers/scsi/lpfc and it's dated October 2026 — go read it again, it's giving main character energy 💜✨

📦 where this page comes from