i40e_vc_get_max_frame_size(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME

i40e_vc_get_max_frame_size — okay so bestie, the original page literally leaves this blank 😭 like the kernel devs wrote the dash and then just... nothing. No description. Iconic of them, honestly. It's a kernel API manual page, and the function does what the title says: it gets the max frame size (for a VF), but the NAME line itself is just i40e_vc_get_max_frame_size - and then silence. We love a mysterious queen 💅

✨ SYNOPSIS

u16 i40e_vc_get_max_frame_size (struct i40e_vf *vf );

So it takes one thing and it gives back a u16. That's the whole vibe 🎀

🫶 ARGUMENTS

  • vf — pointer to the VF. That's it, that's the argument, she's a pointer to a struct i40e_vf and she's the main character of this function 🌸

🌸 DESCRIPTION

Okay so here's the tea 🍵 — the max frame size is determined based on two things: the current port's max frame size, and whether a port VLAN is configured on this VF. Both of those, together, decide the answer.

And here's the messy part 🙈 — the VF is not aware whether it's in a port VLAN. Like, the VF genuinely does not know. So the PF has to account for this in max frame size checks and when it's sending the max frame size to the VF. The PF is doing the emotional labor of remembering the VLAN situation on the VF's behalf, fr fr 🫶

Not me feeling bad for the PF carrying all that context alone 😭

🦋 SEE ALSO

The kernel file this lives in: ./drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c — go read it, iykyk 💖

And now the extended family, all of them, every single one (no gatekeeping here bestie 👑):

✨ that's the whole page, bestie ✨ sourced from ./drivers/net/ethernet/intel/i40e, dated October 2026, and the page we just read is i40e_vc_get_max_frame_size(9). mwah 💋 go read some kernel source, it's giving scholar energy 🎀🦋

📦 where this page comes from