lpfc_nvme_prep_io_cmd(9)

💖 NAME 💖

okay so this is lpfc_nvme_prep_io_cmd(9), straight out of the Kernel API Manual, and its whole vibe is: Issue an NVME-over-FCP IO. That's the name line, bestie — short, iconic, to the point. 💅

✨ SYNOPSIS ✨

Here's the signature exactly as it is, no cap:

int lpfc_nvme_prep_io_cmd (struct lpfc_vport *vport , struct lpfc_io_buf
       *lpfc_ncmd , struct lpfc_nodelist *pnode , struct lpfc_fc4_ctrl_stat
       *cstat );

🎀 ARGUMENTS 🎀

• vport — pointer to a host virtual N_Port data structure. literally the vport pointer, slay.
• lpfc_ncmd — Pointer to lpfc scsi command. yes, with that capital P, we keep it.
• pnode — pointer to a node-list data structure.
• cstat — pointer to the control status structure.

💫 DESCRIPTION 💫

So the driver registers this routine as it io request handler — that's the original wording, and we're not fixing it, we're respecting the lore. 😌

This routine issues an fcp WQE with data from the lpfc_nvme_fcpreq data structure to the rport indicated in lpfc_nvme_rport. Periodt. That's the whole flow described here.

Return value: 0 - Success. Also, the doc literally has TODO: What are the failure codes. — so the failure codes are marked TODO right there, bestie. Not me being vague, that's the source. 😭

🦋 SEE ALSO 🦋

Kernel file: ./drivers/scsi/lpfc/lpfc_nvme.c

• lpfc_nvme_create_queue(9)
• lpfc_nvme_delete_queue(9)
• lpfc_nvme_handle_lsreq(9)
• __lpfc_nvme_ls_req_cmp(9)
• __lpfc_nvme_ls_req(9)
• lpfc_nvme_ls_req(9)
• __lpfc_nvme_ls_abort(9)
• lpfc_nvme_ls_abort(9)
• lpfc_nvme_prep_io_dma(9)
• lpfc_nvme_fcp_io_submit(9)
• lpfc_nvme_abort_fcreq_cmpl(9)
• lpfc_nvme_fcp_abort(9)
• lpfc_release_nvme_buf(9)
• lpfc_nvme_create_localport(9)
• lpfc_nvme_destroy_localport(9)
• lpfc_sli4_nvme_pci_offline_aborted(9)
• lpfc_sli4_nvme_xri_aborted(9)
• lpfc_nvme_wait_for_io_drain(9)
• lpfc_nvme_flush_abts_list(9)
• lpfc_nvmels_flush_cmd(9)

mwah 💋 — this lpfc_nvme_prep_io_cmd(9) page came from source/version ./drivers/scsi/lpfc and is dated October 2026. bye bestie! 💖