lpfc_nvmet_prep_ls_wqe(9)

💖 lpfc_nvmet_prep_ls_wqe(9) 💖

okay so bestie, welcome to the Kernel API Manual — this page is literally all about lpfc_nvmet_prep_ls_wqe(9), and it is giving “get that lpfc wqe data structure allocated and prepared” energy. slay. 💅

---

🌸 NAME 🌸

lpfc_nvmet_prep_ls_wqe — allocate and prepare a lpfc wqe data structure. that’s the assignment, and it ate. ✨

✨ SYNOPSIS ✨

struct lpfc_iocbq * lpfc_nvmet_prep_ls_wqe (struct lpfc_hba *phba ,
       struct lpfc_async_xchg_ctx *ctxp , dma_addr_t rspbuf , uint16_t rspsize
       );

🎀 ARGUMENTS 🎀

• phba — pointer to a host N_Port data structure. host N_Port moment, no cap. 🫶
• ctxp — context info for NVME LS Request. yes, the context bestie.
• rspbuf — DMA buffer of NVME command. buffer vibes.
• rspsize — size of the NVME command. literally the size.

💅 DESCRIPTION 💅

okay so here’s the vibe: this routine allocates a lpfc-WQE data structure from the driver lpfc-WQE free-list, then prepares the WQE with the parameters passed into the routine — all so the discovery state machine can issue Extended Link Service (NVME) commands. iconic behavior. 🌟

It’s a generic lpfc-WQE allocation and preparation routine that all the discovery state machine routines use. The NVME command-specific fields are not set here — they get set up later by the individual discovery machine routines after they call this routine to allocate and prepare a generic WQE data structure. periodt.

It fills in the Buffer Descriptor Entries (BDEs), and it allocates buffers for both command payload and response payload (if expected). 🍓

The reference count on the ndlp is incremented by 1, and the reference to the ndlp is put into context1 of the WQE data structure. that’s so this WQE can hold the ndlp reference for the command’s callback function to access later. iykyk. 🔥

Return code — pointer to the newly allocated/prepared nvme wqe data structure. and when it goes sideways: NULL — when nvme wqe data structure allocation/preparation failed. 😭

🦋 SEE ALSO 🦋

Kernel file ./drivers/scsi/lpfc/lpfc_nvmet.c — go look, bestie. also these functions are in the group chat:

• __lpfc_nvme_xmt_ls_rsp_cmp(9)
• lpfc_nvmet_xmt_ls_rsp_cmp(9)
• lpfc_nvmet_ctxbuf_post(9)
• lpfc_nvmet_xmt_fcp_op_cmp(9)
• __lpfc_nvme_xmt_ls_rsp(9)
• lpfc_nvmet_xmt_ls_rsp(9)
• lpfc_nvmet_ls_req_cmp(9)
• lpfc_nvmet_ls_req(9)
• lpfc_nvmet_ls_abort(9)
• lpfc_sli4_nvmet_xri_aborted(9)
• lpfc_nvmet_handle_lsreq(9)
• lpfc_nvmet_unsol_fcp_buffer(9)
• lpfc_nvmet_unsol_fcp_event(9)
• lpfc_nvmet_sol_fcp_abort_cmp(9)
• lpfc_nvmet_unsol_fcp_abort_cmp(9)
• lpfc_nvmet_xmt_ls_abort_cmp(9)
• lpfc_nvme_unsol_ls_issue_abort(9)
• lpfc_nvmet_invalidate_host(9)

xoxo, from ./drivers/scsi/lpfc, dated October 2026, on the lpfc_nvmet_prep_ls_wqe(9) page 💖