lpfc_sli4_fcf_pri_list_add(9)
π lpfc_sli4_fcf_pri_list_add(9) β yeah it's a kernel manpage bestie
okay so real talk, this page is from the Kernel API Manual and it's all about lpfc_sli4_fcf_pri_list_add β a little function that slots an FCF record into a priority list. it's giving "niche driver internals that only three people on earth need", but we're gonna learn it anyway because that's just who we are π
β¨ NAME β¨
lpfc_sli4_fcf_pri_list_add β
and that's it. that's the whole NAME section. no one-liner. no description. it's giving mysterious. main character energy with zero exposition π«Ά (the original page literally leaves it blank, so we're leaving it blank too. iconique.)
πΈ SYNOPSIS πΈ
int lpfc_sli4_fcf_pri_list_add (struct lpfc_hba *phba , uint16_t
fcf_index , struct fcf_record *new_fcf_record );
literally just three args and an int coming back at you β¨
π ARGUMENTS π
phbaβ pointer tolpfchba data structure. that's the host bus adapter, bestie, say it with me π¦fcf_indexβ the index of the fcf record to add. very demure, very index-y.new_fcf_recordβ pointer to a new FCF record. and ok this one has lore, so buckle up π this routine checks the priority of thefcf_indexto be added. so:- if it's a lower priority than the current head of the
fcf_prilist, then it gets added to the list in the right order β¨ - if it's the same priority as the current head of the list, then it's added to the head of the list and its bit in the
rr_bmaskis set π - if the
fcf_indexto be added is of a higher priority than the current head of the list, then therr_bmaskis cleared, its bit is set in therr_bmask, and it's added to the head of the list π
- if it's a lower priority than the current head of the
so likeβ¦ lower = sorted in place, same = front of the line + bit on, higher = wipe the mask, set the bit, front of the line. three whole vibes. no cap π₯
β RETURN β
0=success 1=failure
zero means slay, one means π. that's the whole spectrum.
π SEE ALSO π
first up, the kernel file where all this lives:
Kernel file ./drivers/scsi/lpfc/lpfc_hbadisc.c
and then a frankly unhinged amount of friends β honestly this is giving "followed by 51 of my closest mutuals":
lpfc_check_inactive_vmid_one(9)lpfc_check_inactive_vmid(9)lpfc_check_nlp_post_devloss(9)lpfc_dev_loss_tmo_handler(9)lpfc_sli4_post_dev_loss_tmo_handler(9)lpfc_alloc_fast_evt(9)lpfc_free_fast_evt(9)lpfc_send_fastpath_evt(9)lpfc_sli4_clear_fcf_rr_bmask(9)lpfc_fab_name_match(9)lpfc_sw_name_match(9)lpfc_mac_addr_match(9)__lpfc_update_fcf_record_pri(9)lpfc_copy_fcf_record(9)__lpfc_update_fcf_record(9)lpfc_register_fcf(9)lpfc_match_fcf_conn_list(9)lpfc_check_pending_fcoe_event(9)lpfc_sli4_new_fcf_random_select(9)lpfc_sli4_fcf_rec_mbox_parse(9)lpfc_sli4_log_fcf_record_info(9)lpfc_sli4_fcf_record_match(9)lpfc_sli4_fcf_rr_next_proc(9)lpfc_sli4_fcf_pri_list_del(9)lpfc_sli4_set_fcf_flogi_fail(9)lpfc_mbx_cmpl_fcf_scan_read_fcf_rec(9)lpfc_mbx_cmpl_fcf_rr_read_fcf_rec(9)lpfc_mbx_cmpl_read_fcf_rec(9)lpfc_init_vfi_cmpl(9)lpfc_issue_init_vfi(9)lpfc_init_vpi_cmpl(9)lpfc_issue_init_vpi(9)lpfc_start_fdiscs(9)lpfc_create_static_vport(9)lpfc_issue_gidpt(9)lpfc_initialize_node(9)lpfc_nlp_logo_unreg(9)lpfc_unreg_hba_rpis(9)lpfc_find_vport_by_vpid(9)lpfc_fcf_inuse(9)lpfc_unregister_vfi_cmpl(9)lpfc_unregister_fcfi_cmpl(9)lpfc_unregister_fcf_prep(9)lpfc_sli4_unregister_fcf(9)lpfc_unregister_fcf_rescan(9)lpfc_unregister_fcf(9)lpfc_unregister_unused_fcf(9)lpfc_read_fcf_conn_tbl(9)lpfc_read_fcoe_param(9)lpfc_get_rec_conf23(9)lpfc_parse_fcoe_conf(9)
heads up bestie: lpfc_unregister_fcf(9) really does show up twice in the original list. that's not me being messy, that's the manpage being messy. we keep it exactly as it is π
and that's the whole page π§ ok bye, this came from ./drivers/scsi/lpfc and it's dated October 2026 β so yes, it's from the future, and yes, the future still has FCF priority lists π 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