lpfc_config_async(9)
π lpfc_config_async(9) β the girlies' guide to the Kernel API Manual β¨
okay so welcome to lpfc_config_async, bestie!! this one lives in the Kernel API Manual and it's lowkey a little setup goblin β it doesn't do the thing, it just gets the mailbox command ready to do the thing. we love a prep queen π
β¨ NAME β¨
lpfc_config_async β prepare a mailbox command for enabling HBA async event. that's it, that's the whole vibe π
π¦ SYNOPSIS π¦
void lpfc_config_async (struct lpfc_hba * phba , LPFC_MBOXQ_t * pmb ,
uint32_t ring );
literally three args, no return value (it's void, so don't go looking for one, she's not giving π)
πΈ ARGUMENTS πΈ
phbaβ pointer to lpfc hba data structure. your HBA's whole personality lives here πpmbβ pointer to the driver internal queue element for mailbox command. this is the little envelope we're stuffing π¬ringβ ring number for the asynchronous event to be configured. pick your ring, bestie, that's where the events are gonna get posted β¨
π DESCRIPTION π
so the asynchronous event enable mailbox command is the one that enables the asynchronous event posting via the ASYNC_STATUS_CN IOCB response β and it also specifies the default ring to which events are posted. iykyk π
this routine prepares the mailbox command for enabling HBA asynchronous event support on a IOCB ring. no cap, that's the whole job β she preps, she doesn't fire π«Ά
β SEE ALSO β
Kernel file ./drivers/scsi/lpfc/lpfc_mbox.c β go read the source, it's giving main character energy:
lpfc_mbox_rsrc_prep(9), lpfc_mbox_rsrc_cleanup(9), lpfc_dump_static_vport(9), lpfc_down_link(9), lpfc_dump_mem(9), lpfc_dump_wakeup_param(9), lpfc_read_nv(9), lpfc_heart_beat(9), lpfc_read_topology(9), lpfc_clear_la(9), lpfc_config_link(9), lpfc_config_msi(9), lpfc_init_link(9), lpfc_read_sparam(9), lpfc_unreg_did(9), lpfc_read_config(9), lpfc_read_lnk_stat(9), lpfc_reg_rpi(9), lpfc_unreg_login(9), lpfc_sli4_unreg_all_rpis(9), lpfc_reg_vpi(9), lpfc_unreg_vpi(9), lpfc_config_pcb_setup(9), lpfc_read_rev(9), lpfc_build_hbq_profile2(9), lpfc_build_hbq_profile3(9), lpfc_build_hbq_profile5(9), lpfc_config_hbq(9), lpfc_config_ring(9), lpfc_config_port(9), lpfc_kill_board(9), lpfc_mbox_put(9), lpfc_mbox_get(9), __lpfc_mbox_cmpl_put(9), lpfc_mbox_cmpl_put(9), lpfc_mbox_cmd_check(9), lpfc_mbox_dev_check(9), lpfc_mbox_tmo_val(9), lpfc_sli4_mbx_sge_set(9), lpfc_sli4_mbx_sge_get(9), lpfc_sli4_mbox_cmd_free(9), lpfc_sli4_config(9), lpfc_sli4_mbox_rsrc_extent(9), lpfc_sli_config_mbox_subsys_get(9), lpfc_sli_config_mbox_opcode_get(9), lpfc_sli4_mbx_read_fcf_rec(9), lpfc_request_features(9), lpfc_init_vfi(9), lpfc_reg_vfi(9), lpfc_init_vpi(9), lpfc_unreg_vfi(9), lpfc_sli4_dump_cfg_rg23(9), lpfc_reg_fcfi(9), lpfc_reg_fcfi_mrq(9), lpfc_unreg_fcfi(9), lpfc_resume_rpi(9)
like, that's a whole friend group right there ππ
ngl, if you're enabling async events, make sure your ring is actually a ring you meant to pick β she takes the number at face value, no vibe check on your behalf π
alright bestie, that's the page!! this one came from <pink>./drivers/scsi/lpfc</pink>, dated October 2026, and it's filed under lpfc_config_async(9) β stan a kernel manpage that knows exactly what she is β¨ππ
π¦ 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