lpfc_build_hbq_profile2(9)
π lpfc_build_hbq_profile2 β the lpfc_build_hbq_profile2(9) kernel API page, but make it make sense β¨
okay so bestie, we're in the kernel API manual today (yes, the Kernel API Manual one) and this little function is genuinely so specific and I love that for her π
πΈ NAME πΈ
lpfc_build_hbq_profile2 β set up the HBQ Selection Profile 2 π
β¨ SYNOPSIS β¨
void lpfc_build_hbq_profile2 (struct config_hbq_var *hbqmb , struct
lpfc_hbq_init *hbq_desc );
like, it returns void, it takes two pointers, and it's giving "I do one thing and I do it well" energy π
π¦ ARGUMENTS π¦
hbqmbβ pointer to the HBQ configuration data structure in the mailbox command. think of it as the lil clipboard she's gonna write on πhbq_descβ pointer to the HBQ selection profile descriptor. the blueprint, the vibe reference, the inspo board π¨
π DESCRIPTION π
so the Host Buffer Queue (HBQ) Selection Profile 2 works like this, bestie: it specifies that the HBA tests the incoming frames' R_CTL/TYPE fields with words 10:15, and then it performs the Sequence Length Test using the fields that live in the Selection Profile 2 extension in words 20:31. two little field-ranges, two very specific jobs, no cap π«Ά
that's it. that's the whole personality. and honestly? iconic β
π SEE ALSO π
the kernel file is ./drivers/scsi/lpfc/lpfc_mbox.c and honestly the whole friend group is here β say hi to all of them, in this exact order, no skipping anyone or it'll be awkward π:
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_config_async(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_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)
(no, I did not lose any of them, and yes, __lpfc_mbox_cmpl_put(9) has a double underscore because she's special π)
okay that's the whole page, mwah π this came from ./drivers/scsi/lpfc and the manual says October 2026, lpfc_build_hbq_profile2(9) β so like, future-dated and flawless, main character energy fr fr ππ
π¦ 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