fcoe_ctlr_fcoe_size(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fcoe_ctlr_fcoe_size(9) — the Kernel API Manual, bestie edition ✨

Okay so real quick, before we even start: this is a page from the Kernel API Manual (yes, the kernel, the big scary one) and it's about fcoe_ctlr_fcoe_size. Don't run away, it's actually so chill. 🫶

🌸 NAME 🌸

fcoe_ctlr_fcoe_size — returns the maximum FCoE size required for a VN_Port. That's it. That's the whole job. Lowkey iconic for how simple it is. 💖

✨ SYNOPSIS ✨

u32 fcoe_ctlr_fcoe_size (struct fcoe_ctlr *fip);

Look at her. Returns a u32, takes one pointer, no drama, no hidden surprises. We love a predictable queen. 👑

🎀 ARGUMENTS 🎀

  • fip — the FCoE controller you're pulling the max FCoE size from. Like, "hey bestie, what's your size" but for controllers. 🦋

💅 DESCRIPTION 💅

So basically: this gives you back the maximum packet size, and that number includes the FCoE header and the FCoE trailer. 📦

But — and this is the important bit, so listen — it does not include any Ethernet headers or VLAN headers. Not one of them. If you were expecting those to be counted in, nope, not today. 🙈

⭐ SEE ALSO ⭐

Kernel file ./drivers/scsi/fcoe/fcoe_ctlr.c — aka where the actual code lives, go say hi 🧚

And literally the entire friend group of FCoE functions, no cap, here they all are:

Sixty of them. Sixty!! That's a whole group chat right there and every single one ate. 🔥

That's the whole page, bestie — go forth and compute your sizes correctly 💜

Big sign-off energy: this one lives in ./drivers/scsi/fcoe, it's dated October 2026, and it's filed under fcoe_ctlr_fcoe_size(9) in the Kernel API Manual. Periodt. 🎀💖✨

📦 where this page comes from