ice_sched_a..._to_hw_layer(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ice_sched_add_nodes_to_hw_layer(9) 💅

ok so bestie, this is a page from the Kernel API Manual and it's about one little function that helps the ice driver build out its scheduling tree. it's giving "construction crew but make it silicon" 🏗️✨

✨ NAME ✨

ice_sched_add_nodes_to_hw_layer — literally adds nodes to a HW layer. that's the whole vibe. 🎀

🌸 SYNOPSIS 🌸

int ice_sched_add_nodes_to_hw_layer (struct ice_port_info *pi , struct
ice_sched_node *tc_node , struct ice_sched_node *parent , u8 layer , u16
num_nodes , u32 *first_node_teid , u16 *num_nodes_added );

🦋 ARGUMENTS 🦋

okay so here's who's coming to the party, keep up 💖

  • pi — the port information structure. it's the port's whole little info hub, no cap.
  • tc_node — pointer to the TC node. that's your traffic-class node, main character of this subtree 🌈
  • parent — pointer to the parent node. everybody's got a parent, it's fine 🙈
  • layer — the layer number where you wanna add the nodes. pick your floor, bestie ✨
  • num_nodes — how many nodes you're adding. yes the count matters, don't be shy 💅
  • first_node_teid — pointer to the first node TEID. it's a pointer, so it can hand info back to you, iykyk 🫶
  • num_nodes_added — pointer to the number of nodes added. also a pointer. also giving info back. we love a two-way street 😭

🔥 DESCRIPTION 🔥

short and sweet: this function adds nodes into a specific HW layer. that's it, that's the whole thing 💀✨

like, you point it at a parent in your scheduling tree, you tell it which layer and how many nodes, and it goes and does the thing. iconic behavior honestly 👑

💜 SEE ALSO 💜

the friend group is huge, so buckle up 🧚‍♀️ — these all live in the kernel file ./drivers/net/ethernet/intel/ice/ice_sched.c 🍓

🎀 a lil sign-off 🎀

this page came from ./drivers/net/ethernet/intel/ice, dated October 2026 — so like, fully future-dated, we stan a time traveler ⭐💖 go build your scheduling tree bestie, you got this 🫶✨

📦 where this page comes from