lpfc_sli4_fcf_record_match(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the lpfc_sli4_fcf_record_match(9) page from the Kernel API Manual β€” yes, we’re doing kernel FCF record matching today, and honestly? iconic behavior πŸ’…βœ¨

🌸 NAME 🌸

lpfc_sli4_fcf_record_match - testing new FCF record for matching existing FCF

✨ SYNOPSIS ✨

okay so here’s the signature, bestie β€” copy it exactly, spacing and all, no β€œfixing” the punctuation:

bool lpfc_sli4_fcf_record_match (struct lpfc_hba *phba , struct
       lpfc_fcf_rec *fcf_rec , struct fcf_record *new_fcf_record , uint16_t
       new_vlan_id );

πŸŽ€ ARGUMENTS πŸŽ€

  • phba β€” pointer to lpfc hba data structure. main-character pointer energy, honestly.
  • fcf_rec β€” pointer to an existing FCF record.
  • new_fcf_record β€” pointer to a new FCF record.
  • new_vlan_id β€” vlan id from the new FCF record.

πŸ¦‹ DESCRIPTION πŸ¦‹

So this function performs matching test of a new FCF record against an existing FCF record. like a vibe check, but make it FCF records 🫢

If the new_vlan_id passed in is LPFC_FCOE_IGNORE_VID, then vlan id will not be used as part of the FCF record matching criteria β€” it’s lowkey sitting that round out πŸ’…

It returns true if all the fields matching, otherwise returns false. no cap: all fields or nothing 😭πŸ”₯

πŸ’– SEE ALSO πŸ’–

Kernel file ./drivers/scsi/lpfc/lpfc_hbadisc.c β€” go read it, bestie.


mwah πŸ’‹ β€” source path: ./drivers/scsi/lpfc, date: October 2026, page: lpfc_sli4_fcf_record_match(9). that’s the whole cute little kernel moment, bestie 🌈🫢

πŸ“¦ where this page comes from