lpfc_bsg_is...box_ext_cmpl(9)
π lpfc_bsg_issue_read_mbox_ext_cmpl β a Kernel API Manual moment π
okay bestie, so this is a page straight out of the Kernel API Manual, and the star of the show has a name so long the header had to abbreviate it: lpfc_bsg_is...box_ext_cmpl(9). iconic behavior tbh. let's get into it π¦
β¨ NAME β¨
lpfc_bsg_issue_read_mbox_ext_cmpl β the compl handler for multi-buffer read mbox π
(yes, "compl" = completion, she's just vibing with the shorthand, iykyk)
πΈ SYNOPSIS πΈ
void lpfc_bsg_issue_read_mbox_ext_cmpl (struct lpfc_hba *phba ,
LPFC_MBOXQ_t *pmboxq );
like, that's the whole signature. no return value, she returns void, she's mysterious like that π
π ARGUMENTS π
phbaβ pointer to the HBA context object. literally the context bestie, the whole vibe of the host bus adapter π«Άpmboxqβ pointer to the mailbox command. the actual mbox in question, the main character π
π DESCRIPTION π
so what does she do? she's the completion handler function for mailbox read commands with multiple external buffers. that's it, that's the whole job. when a multi-buffer read mbox finishes, this is the girl who gets the callback. no cap, she handles the completion. β¨π₯
π¦ SEE ALSO π¦
first up, the kernel file where all this lives (verbatim, do not @ me):
./drivers/scsi/lpfc/lpfc_bsg.c
and now the whole squad, every single one, no skipping, periodt:
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_cmp(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_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)
lowkey that's a lot of friends but she's got range, okay? go read ./drivers/scsi/lpfc/lpfc_bsg.c and tell them I said hi π
and that's the page!! sourced from ./drivers/scsi/lpfc, dated October 2026, filed under lpfc_bsg_is...box_ext_cmpl(9) in the Kernel API Manual. slay, stay compliant, drink water, bye bestie ππ§β¨
π¦ 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