lpfc_sli4_fcf_pri_list_del(9)
π lpfc_sli4_fcf_pri_list_del(9) π
okay so bestie, we're in the Kernel API Manual today and this page is literally called lpfc_sli4_fcf_pri_list_del(9) β say that five times fast, i dare you π she's a mouthful but she's iconic.
β¨ NAME β¨
lpfc_sli4_fcf_pri_list_del β
so, the original page leaves the description blank. like, fully empty. no notes. she said "my name is enough" and honestly? main character energy π we respect it.
π¦ SYNOPSIS π¦
void lpfc_sli4_fcf_pri_list_del (struct lpfc_hba *phba , uint16_t
fcf_index );
note the void bestie β she's not giving you anything back, she just does the thing and leaves π
π ARGUMENTS π
phbaβ pointer to lpfc hba data structure. that's the hba, the whole vibe, the main character struct π«Άfcf_indexβ the index of the fcf record to delete. and then the page drops the actual lore right here, so let's break it down:- this routine checks the on list flag of the
fcf_indexto be deleted π - if it is one the list β i.e. on the list β then it is removed from the list, and the flag is cleared β¨
- this routine grab the
hbalockbefore removing the fcf record from the list π
- this routine checks the on list flag of the
no cap, the locking part is the whole point: hbalock gets grabbed before that fcf record leaves the list. do not skip the lock, bestie, that's how you end up in a race condition and we are NOT doing that today π
π SEE ALSO π
kernel file ./drivers/scsi/lpfc/lpfc_hbadisc.c β that's where she lives, go say hi π
and now the guest list, because this function knows everyone and she wants you to know them too. 51 entries, not one of them skipped, i would never do you like that π«Ά
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_set_fcf_flogi_fail(9)lpfc_sli4_fcf_pri_list_add(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)
she really said "i have a friend for every occasion" and honestly? slay πΈ
and that's the whole page bestie, no crumbs left behind π she's from <pink>./drivers/scsi/lpfc</pink>, dated October 2026, and her full legal name is lpfc_sli4_fcf_pri_list_del(9) β memorize it, put it on a friendship bracelet, whatever you gotta do πβ¨π
π¦ 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