iavf_get_max_vlans_allowed(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 iavf_get_max_vlans_allowed — bestie edition 🦋

okay so real quick, this lil page lives in the Kernel API Manual (section 9, kernel land, not for the faint of heart 💅) and it's all about iavf_get_max_vlans_allowed. yes that's a mouthful, yes we're gonna get through it together.

✨ NAME ✨

iavf_get_max_vlans_allowed — get the maximum VLANs allowed for this VF 🎀

like, the actual cap. the ceiling. the "how many VLANs can this VF even have" number.

🌸 SYNOPSIS 🌸

u16 iavf_get_max_vlans_allowed (struct iavf_adapter *adapter );

she takes one pointer and hands you back a u16. simple. iconic. no cap.

🧚 ARGUMENTS 🧚

  • adapter — board private structure. that's the big ol' struct holding everything this driver knows about the device, and yeah, you gotta pass it in 💖

🔥 DESCRIPTION 🔥

okay so the whole vibe here is: it depends on the negotiated VLAN capability. that's the main character of this function, the negotiation.

  • for VIRTCHNL_VF_OFFLOAD_VLAN, do not impose a limit — that keeps the current behavior exactly as it was, no changes, no drama 🙈
  • for VIRTCHNL_VF_OFFLOAD_VLAN_V2, use the maximum allowed that was sent from the PF. the PF said a number, we're using that number, periodt ⭐

so like, depending on which flavor you negotiated, you either get "no limit, we're chilling" or "here's your exact number from the PF." two paths, both valid, both slay 💅

🌈 SEE ALSO 🌈

the source file itself lives at Kernel file ./drivers/net/ethernet/intel/iavf/iavf_main.c — go read it, it's giving lore 👑

and here's the whole friend group, every single one, no one left behind 🫶:

and that's the whole page, bestie 💜 it ships from ./drivers/net/ethernet/intel/iavf and it's dated October 2026 — so like, mark your calendar, page iavf_get_max_vlans_allowed(9) is filed under both the source path and the date, mwah 🎀✨

📦 where this page comes from