fcoe_oem_match(9)

📦 version 7.3.1, in nixpkgs unstable

💖 fcoe_oem_match(9) — the Kernel API Manual glow-up 💖

okay so bestie, welcome to the fcoe_oem_match page from the Kernel API Manual ✨ this one is short and sweet and honestly kind of iconic — it's the little matchmaker function that decides whether an offloaded exchange manager gets the packet or not. let's get into it 🎀

✨ NAME ✨

fcoe_oem_match — the match routine for the offloaded exchange manager 👑

🦋 SYNOPSIS 🦋

bool fcoe_oem_match (struct fc_frame *fp );

🌸 ARGUMENTS 🌸

  • fp — the I/O frame 💅 like, the actual frame we're deciding about

💜 DESCRIPTION 💜

so this routine gets associated with an exchange manager (aka an EM, iykyk). when the libfc exchange handling code is out here looking for an EM to use, it calls this routine and hands it the frame it wants to send 🫶

this routine returns True if the associated EM is the one to be used, and False if the echange code should keep looking for an EM. (yes, "echange" — that's how it's spelled in the source, not me being chaotic, okay 😭)

the offload EM that this routine is associated with will handle any packets that are for SCSI read requests 📖✨

and plot twist — this has been enhanced to work when the FCoE stack is operating in target mode 🔥 she's versatile!

⭐ RETURN ⭐

True for read types I/O, otherwise returns false. no cap 💯

🌈 SEE ALSO 🌈

the kernel file ./drivers/scsi/fcoe/fcoe.c and honestly the whole friend group:

💀 reminder bestie: this page lives in the kernel tree at ./drivers/scsi/fcoe, so go touch grass in that directory if you need more context 🌱

and that's the whole page, bestie — slay 💅✨ dropping from ./drivers/scsi/fcoe, dated October 2026, in the Kernel API Manual, fcoe_oem_match(9) herself. mwah 🫶🎀💖

📦 where this page comes from