fcoe_ctlr_vn_beacon(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– fcoe_ctlr_vn_beacon(9) β€” handle received beacon πŸ’–

okay so bestie, welcome to fcoe_ctlr_vn_beacon(9) from the Kernel API Manual β€” yes, that’s the whole title vibe. This one is literally about handling a received beacon, and we’re gonna get into it. βœ¨πŸŽ€


✨ NAME ✨

fcoe_ctlr_vn_beacon β€” handle received beacon. That’s the name, that’s the job, periodt. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

okay so the signature is giving:

void fcoe_ctlr_vn_beacon (struct fcoe_ctlr *fip , struct fcoe_rport *new
       );

🌸 ARGUMENTS 🌸

  • fip β€” the FCoE controller that received the frame. πŸ’–
  • new β€” the newly-parsed FCoE rport from the Beacon. πŸ‘‘

πŸ’… DESCRIPTION πŸ’…

okay so the whole plot: this is the handler for a received beacon. That’s the tea. β˜•βœ¨

Heads up, no cap: it’s called with ctlr_mutex held. πŸ”’ Periodt.


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/scsi/fcoe/fcoe_ctlr.c β€” plus the whole icon squad of related calls:


okay that’s the whole page, bestie πŸ’– this one comes from the Kernel API Manual, source ./drivers/scsi/fcoe, dated October 2026, and it’s all about fcoe_ctlr_vn_beacon(9). periodt. πŸŽ€βœ¨

πŸ“¦ where this page comes from