ice_sched_cfg_vsi(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ice_sched_cfg_vsi — like, the VSI glow-up function

okay so bestie, welcome to the Kernel API Manual (yes, that's the manual name, we stan a whole manual) ✨

This page is all about ice_sched_cfg_vsi — the function that configures the new/existing VSI. It's giving backstage-pass-to-the-scheduler energy, no cap 🎀

🌸 SYNOPSIS 🌸

int ice_sched_cfg_vsi (struct ice_port_info *pi , u16 vsi_handle , u8 tc
, u16 maxqs , u8 owner , bool enable );

Like, one function, six arguments, and honestly? She ate. 🔥

🫶 ARGUMENTS 🫶

  • pi — the port information structure. main character struct fr 💖
  • vsi_handle — the software VSI handle. iykyk 💅
  • tc — the TC number ✨
  • maxqs — max number of queues. literally the queue budget, don't blow it 😭
  • owner — LAN or RDMA. pick your lane bestie 🦋
  • enable — TC enabled or disabled 🌈

👑 DESCRIPTION 👑

So here's the vibe check 🔍 — this function adds/updates VSI nodes based on the number of queues. That's the whole gig.

And then there's the suspend/resume drama, which honestly has the best plotline:

  • If TC is enabled and the VSI is in suspended state, then resume the VSI back. welcome back queen 🫶✨
  • If TC is disabled, then suspend the VSI — but only if it is not already. like, don't double-suspend, that's not the moment 🙈
no cap, the wording "if it is not already" is doing a lot of heavy lifting here. respect it. 💀

🧚 SEE ALSO 🧚

The kernel file is right here bestie: ./drivers/net/ethernet/intel/ice/ice_sched.c 🍓

And now… the friend group. It's large. It's iconic. It's every single one, and we're not skipping a single name 💜

okay that's genuinely the whole list, we did it, group hug 🫶💖

bye bestie!! this page came from ./drivers/net/ethernet/intel/ice, dated October 2026, and it's the ice_sched_cfg_vsi(9) page — slay, periodt ✨🎀💅

📦 where this page comes from