ice_vsi_cfg_frame_size(9)

📦 version 7.3.1, in nixpkgs unstable

✨ ice_vsi_cfg_frame_size ✨

Okay so real talk, bestie — you're looking at a page from the Kernel API Manual, and it's all about ice_vsi_cfg_frame_size. It's a function, it's in the kernel, and it's about to make your Rx ring look correct. 💅

🌸 NAME 🌸

ice_vsi_cfg_frame_size — literally here to set up the max frame size and the Rx buffer length. That's the whole job. Slay.

💖 SYNOPSIS 💖

void ice_vsi_cfg_frame_size (struct ice_vsi *vsi , struct ice_rx_ring *ring );

No return value, no drama — it's a void, so it just does the thing and leaves. 🫶

🎀 ARGUMENTS 🎀

  • vsi — the VSI. Yeah that's all the manpage says, but it's the VSI, the main character here. 👑
  • ring — the Rx ring you want to configure. This is the one getting the glow-up. ✨

🦋 DESCRIPTION 🦋

So here's the vibe: this function figures out the maximum frame size and the Rx buffer length that you should be using for a PF VSI — and then it goes and sets both of those in the associated Rx ring structure. 🧚

That's it. That's the whole plot. It determines the values, it stashes them in the ring, done. No cap. 🍓

💜 SEE ALSO 💜

The kernel file lives right here:

./drivers/net/ethernet/intel/ice/ice_base.c

And these are the besties it runs with (iykyk):

And that's the whole page, bestie — no crumbs left behind. 💀✨

Cute little sign-off before you go: this one comes out of ./drivers/net/ethernet/intel/ice, dated October 2026. Stan a stable release date. 🎀🦋💜

📦 where this page comes from