lpfc_issue_ct_rsp_cmp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this page is lpfc_issue_ct_rsp_cmp(9) from the Kernel API Manual, and the actual name is literally lpfc_issue_ct_rsp_cmp β€” lpfc_issue_ct_rsp's completion handler. it’s giving β€œi finish the thing you started” energy, fr fr πŸŽ€


✨ SYNOPSIS ✨

void lpfc_issue_ct_rsp_cmp (struct lpfc_hba *phba , struct lpfc_iocbq *cmdiocbq , struct lpfc_iocbq *rspiocbq );

πŸŽ€ ARGUMENTS πŸŽ€

  • phba β€” pointer to the HBA context object. your whole adapter situation lives here πŸ’…
  • cmdiocbq β€” pointer to the command iocb. the original ask, the main character 🫢
  • rspiocbq β€” pointer to the response iocb. the reply, the β€œand what did they say” moment 🌸

πŸ’… DESCRIPTION πŸ’…

so this function is the completion handler for iocbs issued using the lpfc_issue_ct_rsp_cmp function. yes bestie, that’s what it says, no cap.

it gets called by the ring event handler function with no lock held. periodt. it can be called from both worker thread context and interrupt context. it also can be called from another thread which cleans up the SLI layer objects β€” so like, it has range πŸ’€

what it does: it copies the contents of the response iocb into the response iocb memory object provided by the caller of lpfc_sli_issue_iocb_wait, and then wakes up the thread which sleeps for the iocb completion. that’s the whole vibe: copy the response, wake the sleeper, slay ✨


πŸ¦‹ SEE ALSO πŸ¦‹

kernel file: ./drivers/scsi/lpfc/lpfc_bsg.c β€” go peep it, iykyk πŸ‘‘


mwah πŸ’‹ this lil page came from ./drivers/scsi/lpfc, dated October 2026, and it’s the lpfc_issue_ct_rsp_cmp(9) manual page. iconic, honestly πŸ¦‹βœ¨

πŸ“¦ where this page comes from