ice_vc_vlan_action(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ ice_vc_vlan_action β€” the Kernel API Manual ✨

okay so first things first, bestie: this page is from the Kernel API Manual, section 9, and the star of the show is literally ice_vc_vlan_action. she's a little function, she does one thing, and she does it well πŸ’…


🌸 NAME 🌸

ice_vc_vlan_action β€” the action to perform on the virthcnl_vlan

(and yes, virthcnl_vlan is spelled exactly like that in the source, don't come for me, I'm just the messenger πŸ™ˆ)


✨ SYNOPSIS ✨

ok so here's her whole signature, character for character, no edits, no vibes-based corrections:

int ice_vc_vlan_action (struct ice_vsi *vsi , int (*vlan_action)(struct
ice_vsi *, struct ice_vlan *) , struct ice_vlan *vlan );

she takes three things and she returns an int. that's the whole personality. lowkey iconic πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

three parameters, three besties, let's meet them:

  • vsi β€” the VF's VSI, and she's the one actually used to perform the action. like, she's the venue. the action happens at her. 🫢
  • vlan_action β€” the function to perform the action with (i.e. add/del). yep, you're passing in a function pointer, she's calling it, it's giving callback energy fr fr πŸ’€
  • vlan β€” the VLAN filter to perform the action with. this is the actual thing getting added or deleted, no cap.

so real talk: vsi = where, vlan_action = what operation, vlan = which filter. three-part harmony. ate. πŸ”₯


πŸ’– SEE ALSO πŸ’–

okay this list is long and I'm not skipping a single one of them because every single reference is part of the lore πŸ‘‘

  • Kernel file ./drivers/net/ethernet/intel/ice/virt/virtchnl.c

and now the whole crew, in order, no crumbs left behind:

that's the whole group chat. you're welcome. πŸ«ΆπŸ’œ


ngl, if you're here, you're probably already deep in the virtchnl files. drink some water, bestie. and remember: every reference above keeps its exact (9) suffix, I did not touch a single character of them. 🧚

and that's the page!! source lives over at ./drivers/net/ethernet/intel/i... (yes, truncated in the original, I'm not gonna pretend otherwise πŸ’€) and the date on this whole moment is October 2026. mwah, go read some kernel code, you got this πŸŒˆβ­πŸ“

πŸ“¦ where this page comes from