ice_sched_get_agg_node(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_sched_get_agg_node β€” Kernel API Manual ✨

okay so bestie, welcome to the ice scheduler corner of the kernel, and today's main character is ice_sched_get_agg_node(9) 🫢 it lives in the Kernel API Manual, and it's honestly giving "small function, huge friend group" energy, because look at that SEE ALSO list 😭


🌸 NAME 🌸

ice_sched_get_agg_node β€” get an aggregator node based on aggregator ID πŸ’«


✨ SYNOPSIS ✨

struct ice_sched_node * ice_sched_get_agg_node (struct ice_port_info *pi
, struct ice_sched_node *tc_node , u32 agg_id );

like, that's the whole vibe. it takes stuff, it hands you back a struct ice_sched_node *. no cap πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • pi β€” pointer to the port information structure 🫢 your port's whole info situation.
  • tc_node β€” pointer to the TC node. yes bestie, that TC node, the one you're branching from.
  • agg_id β€” aggregator ID πŸ”₯ the literal number that says which aggregator we're talking about.

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does it actually do? it retrieves an aggregator node for a given aggregator ID β€” from a given TC branch πŸ’– that's it, that's the whole function, and honestly? iconic. you hand it the port info, the TC node, and the ID, and it goes and finds you the matching aggregator node in that branch. periodt ✨

no lies detected: the aggregator ID is what picks the node, and the TC branch is where it looks. iykyk 🌈

πŸ”₯ SEE ALSO πŸ”₯

literally the entire ice scheduler extended universe, bestie β€” go read these too, they're all in the Kernel file ./drivers/net/ethernet/intel/ice/ice_sched.c:


okay that's the page πŸŽ€ one last thing, the receipts: it comes from ./drivers/net/ethernet/intel/ice, dated October 2026, and the page itself is ice_sched_get_agg_node(9). mwah, go forth and schedule πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from