lpfc_bsg_write_ebuf_set(9)
π NAME π
lpfc_bsg_write_ebuf_set β set the next mailbox write external buffer β¨
Okay so real talk, bestie β the NAME section says write but the DESCRIPTION section legit says read. That's literally what the original page says, word for word, so I'm not touching it. Kernel docs stay iconic and slightly chaotic. π
πΈ SYNOPSIS πΈ
int lpfc_bsg_write_ebuf_set (struct lpfc_hba *phba , struct bsg_job *job
, struct lpfc_dmabuf *dmabuf );
It hands you back an int, no cap. β¨
π ARGUMENTS π
phbaβ Pointer to HBA context object. It's the HBA's whole ~situation~, the context of the host bus adapter. Main character energy, honestly. πjobβ Pointer to the job object. The job's here to get done, she has a task and she's serving it. π«Άdmabufβ Pointer to a DMA buffer descriptor. Literally the little name tag for the DMA buffer, so everyone knows which buffer we're talking about. π
π¦ DESCRIPTION π¦
This routine sets up the next mailbox read external buffer obtained from user space through BSG.
Periodt. That's the whole function's vibe β it does the setup for the next mailbox read external buffer, and that buffer came from user space via BSG. π
Yes, the NAME says "write" and this says "read." That's the original, fr fr β I am simply the messenger π§
β¨ SEE ALSO β¨
First off, the kernel file it lives in, bestie:
./drivers/scsi/lpfc/lpfc_bsg.c
And now π the entire squad β every single one of these showed up to the group chat, in the exact order they arrived:
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_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_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)
Fifty-eight (9)-suffixed siblings and every last one of them made the list β nothing skipped, nothing merged, we keep the whole family together π«Άβ¨
And that's the page, bestie! π It ships out of ./drivers/scsi/lpfc, it's dated October 2026, and it answers to the name lpfc_bsg_write_ebuf_set(9). Slay, go read your mailboxes. π
π¦ 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