lpfc_nvme_fcp_io_submit(9)

📦 version 7.3.1, in nixpkgs unstable

💜 lpfc_nvme_fcp_io_submit(9) 💜

okay bestie, so this is a page from the Kernel API Manual and it's all about lpfc_nvme_fcp_io_submit — literally the function that ships an NVME-over-FCP IO out the door. let's get into it 🎀

✨ NAME ✨

lpfc_nvme_fcp_io_submit — Issue an NVME-over-FCP IO 💅

🌸 SYNOPSIS 🌸

int lpfc_nvme_fcp_io_submit (struct nvme_fc_local_port *pnvme_lport ,
struct nvme_fc_remote_port *pnvme_rport , void *hw_queue_handle , struct
nvmefc_fcp_req *pnvme_fcreq );

like, four arguments in, an int out. classic. no cap 🫶

🦋 ARGUMENTS 🦋

  • pnvme_lport — Pointer to the driver's local port data. this is the local port's whole situation, handed to you 💖
  • pnvme_rport — Pointer to the rport getting the lpfc_nvme_ereq. (that's rport as in remote port, she's the one receiving 👑)
  • hw_queue_handle — Driver-returned handle in lpfc_nvme_create_queue. yes, it came back from there, so you already have it 🎀
  • pnvme_fcreq — IO request from nvme fc to driver. this is the actual request being submitted, main character energy fr fr ⭐

🌈 DESCRIPTION 🌈

So the driver registers this routine as its io request handler — that's her job, that's her whole vibe 💅

This routine issues an fcp WQE with data from the lpfc_nvme_fcpreq data structure to the rport indicated in lpfc_nvme_rport. like, it takes the WQE, fills it with the stuff from the fcreq structure, and points it at the rport. slay ✨

Return value : 0 - Success

TODO: What are the failure codes. 😭 yeah bestie the failure codes are literally a mystery here — the page says TODO and we are NOT gonna invent them. if you need them, go read the source, iykyk 💀

🧚 SEE ALSO 🧚

Kernel file ./drivers/scsi/lpfc/lpfc_nvme.c — plus her whole friend group, no cap:

and that's the page!! 🫶

cute lil sign-off bestie: this one lives in ./drivers/scsi/lpfc and it's dated October 2026 — periodt, go read the source, mwah 💖💅🎀

📦 where this page comes from