fnic_fcoe_fi...scovery_resp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ NAME πŸ‘‘

fnic_fcoe_fip_discovery_resp β€” ok so this one processes FCF advertisements and honestly it's giving "the most popular girl in school gets a million messages" energy πŸ’…βœ¨


✨ SYNOPSIS ✨

void fnic_fcoe_fip_discovery_resp (struct fnic *fnic , struct fip_header
*fiph );

πŸŽ€ ARGUMENTS πŸŽ€

  • fnic β€” the handle to your fnic driver instance 🫢 like, this is the whole personality of the driver right here.
  • fiph β€” the received frame fr fr, the actual ad that just slid into your inbox πŸ’Œ

🌸 DESCRIPTION 🌸

Okay bestie, FCF advertisements can be two whole vibes and you need to know both πŸ‘‡

solicited β€” this is when it's sent in response to a "discover FCF" FIP request. So you slide in, ask who's out there, and they respond πŸ¦‹ What we do: store the information of the FCF with the highest priority. And if there are multiple FCFs? We wait until timeout, no cap β€” like, don't rush the group chat, let everyone answer first β³πŸ’–

unsolicited β€” this one is sent periodically by the FCF just for keep alive, it's the "hey just checking in bestie πŸ’•" text. And the rule is: if FLOGI is in progress or completed, and the advertisement is received by our selected FCF, then you refresh the keep alive timer. That's it, that's the whole thing πŸ”₯

ngl the priority + timeout thing matters β€” multiple FCFs showing up at once is real, and you don't just pick the first one that texts back πŸ™ˆ

πŸ’œ SEE ALSO πŸ’œ

Kernel file ./drivers/scsi/fnic/fip.c β€” and the whole friend group, go say hi to all of them:


mwah πŸ’‹ that's the whole page, and it lives in ./drivers/scsi/fnic as of October 2026 β€” fnic_fcoe_fi...scovery_resp(9) stays iconic, periodt 🌈⭐

πŸ“¦ where this page comes from