lpfc_bsg_event_new(9)
π lpfc_bsg_event_new(9) π
ok so this is a page from the Kernel API Manual (lpfc_bsg_event_new(9), section 9, kernel API vibes only) and bestie, it's literally one function: it allocates and initializes an event structure. that's the whole main character moment. no cap. π
β¨ NAME β¨
lpfc_bsg_event_new β allocate and initialize a event structure π¦
(yes, "a event." the kernel said what it said and we respect it π )
πΈ SYNOPSIS πΈ
struct lpfc_bsg_event * lpfc_bsg_event_new (uint32_t ev_mask , int
ev_reg_id , uint32_t ev_req_id );
like, it hands you back a struct lpfc_bsg_event * and takes three lil arguments. that's it. slay. β
π ARGUMENTS π
ev_maskβ Mask of events. π« that's the mask, babe, it's masking events.ev_reg_idβ Event reg id. π«Ά it's anint, it's the event reg id, iconic behaviour honestly.ev_req_idβ Event request id. π₯ auint32_t, and it is, in fact, the event request id.
three args, zero mystery, total vibe check pass. π
π¦ SEE ALSO π¦
ok this is the part where the page goes absolutely feral with cross-references, so buckle up bestie, we're listing every single one and yes i mean every one π
First, the file itself:
- Kernel file
./drivers/scsi/lpfc/lpfc_bsg.c
and now the whole friend group (no skipping, i would never π):
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),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_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)
like... that's the whole extended universe. literally every lpfc_bsg function pulled up to the group chat. iykyk π
ngl if you're looking forlpfc_bsg_event_free(9),lpfc_bsg_event_ref(9)orlpfc_bsg_event_unref(9)β they're up there in the list, they're the event lifecycle besties, go say hi π§
ok final sign-off moment: this page lives in ./drivers/scsi/lpfc and it's dated October 2026 β that's the source/version and date, and honestly? future-dated manpage energy. main character. periodt π
β¨π π
π¦ 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