lpfc_issue_ct_rsp_cmp(9)
π 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 π
lpfc_bsg_send_mgmt_cmd_cmp(9)lpfc_bsg_send_mgmt_cmd(9)lpfc_bsg_rport_els_cmp(9)lpfc_bsg_rport_els(9)lpfc_bsg_event_free(9)lpfc_bsg_event_ref(9)lpfc_bsg_event_unref(9)lpfc_bsg_event_new(9)diag_cmd_data_free(9)lpfc_bsg_ct_unsol_abort(9)lpfc_bsg_hba_set_event(9)lpfc_bsg_hba_get_event(9)lpfc_issue_ct_rsp(9)lpfc_bsg_send_mgmt_rsp(9)lpfc_bsg_diag_mode_enter(9)lpfc_bsg_diag_mode_exit(9)lpfc_sli3_bsg_diag_loopback_mode(9)lpfc_sli4_bsg_set_link_diag_state(9)lpfc_sli4_bsg_set_loopback_mode(9)lpfc_sli4_diag_fcport_reg_setup(9)lpfc_sli4_bsg_diag_loopback_mode(9)lpfc_bsg_diag_loopback_mode(9)lpfc_sli4_bsg_diag_mode_end(9)lpfc_sli4_bsg_link_diag_test(9)lpfcdiag_loop_self_reg(9)lpfcdiag_loop_self_unreg(9)lpfcdiag_loop_get_xri(9)lpfc_bsg_dma_page_alloc(9)lpfc_bsg_dma_page_free(9)lpfc_bsg_dma_page_list_free(9)diag_cmd_data_alloc(9)lpfcdiag_sli3_loop_post_rxbufs(9)lpfc_bsg_diag_loopback_run(9)lpfc_bsg_get_dfc_rev(9)lpfc_bsg_issue_mbox_cmpl(9)lpfc_bsg_check_cmd_access(9)lpfc_bsg_mbox_ext_session_reset(9)lpfc_rd_obj_emb0_handle_job(9)lpfc_bsg_issue_mbox_ext_handle_job(9)lpfc_bsg_issue_read_mbox_ext_cmpl(9)lpfc_bsg_issue_write_mbox_ext_cmpl(9)lpfc_bsg_sli_cfg_read_cmd_ext(9)lpfc_bsg_sli_cfg_write_cmd_ext(9)lpfc_bsg_handle_sli_cfg_mbox(9)lpfc_bsg_mbox_ext_abort(9)lpfc_bsg_read_ebuf_get(9)lpfc_bsg_write_ebuf_set(9)lpfc_bsg_handle_sli_cfg_ebuf(9)lpfc_bsg_handle_sli_cfg_ext(9)lpfc_bsg_issue_mbox(9)lpfc_bsg_mbox_cmd(9)lpfc_check_fwlog_support(9)lpfc_bsg_get_ras_config(9)lpfc_bsg_set_ras_config(9)lpfc_bsg_get_ras_lwpd(9)lpfc_bsg_get_ras_fwlog(9)lpfc_bsg_hst_vendor(9)lpfc_bsg_request(9)lpfc_bsg_timeout(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms