__lpfc_nvme_xmt_ls_rsp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Hey bestie πŸ’– we're in the Kernel API Manual today, and the page is __lpfc_nvme_xmt_ls_rsp(9). It's giving low-level NVME LS response energy, and yes, we're keeping every single detail. Periodt.

🌸 NAME 🌸

__lpfc_nvme_xmt_ls_rsp β€” Generic service routine to issue transmit an NVME LS rsp for a prior NVME LS request that was received.

✨ SYNOPSIS ✨

       int __lpfc_nvme_xmt_ls_rsp (struct lpfc_async_xchg_ctx *axchg , struct
       nvmefc_ls_rsp *ls_rsp , void (*xmt_ls_rsp_cmp)(struct lpfc_hba *phba,
       struct lpfc_iocbq *cmdwqe, struct lpfc_iocbq *rspwqe) );

πŸŽ€ ARGUMENTS πŸŽ€

  • axchg β€” pointer to exchange context for the NVME LS request the response is for. Like, this is the context bestie πŸ’…
  • ls_rsp β€” pointer to the transport LS RSP that is to be sent. Slay, go send it ✨
  • xmt_ls_rsp_cmp β€” completion routine to call upon RSP transmit done. She gets the callback when the transmit is done, no cap 🫢

πŸ’… DESCRIPTION πŸ’…

This routine is used to format and send a WQE to transmit a NVME LS Response. The response is for a prior NVME LS request that was received and posted to the transport. That's the whole vibe: prior request came in, response goes out πŸ”₯

🌈 RETURN 🌈

  • 0 : if response successfully transmit
  • non-zero : if response failed to transmit, of the form -Exxx.

πŸ¦‹ SEE ALSO πŸ¦‹


Okay bye bestie 🫢 This iconic page's source is ./drivers/scsi/lpfc, dated October 2026, and the title is __lpfc_nvme_xmt_ls_rsp(9). Mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from