ice_get_rc_coalesce(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ice_get_rc_coalesce(9) πŸ’–

okay bestie, welcome to the Kernel API Manual β€” yes, we're doing kernel API manual energy today. This page is literally about grabbing ITR values for a specific ring container, and we're gonna make it make sense. No cap. 🫢


🌸 NAME 🌸

ice_get_rc_coalesce β€” get ITR values for specific ring container

✨ SYNOPSIS ✨

int ice_get_rc_coalesce (struct ethtool_coalesce *ec , struct
       ice_ring_container *rc );

πŸ’… ARGUMENTS πŸ’…

  • ec β€” the ethtool structure you're filling with the driver's coalesce settings. It's the container getting the glow-up. ✨
  • rc β€” the ring container where the ITR values will come from. This is the source of truth for this little query. πŸ’–

πŸ”₯ DESCRIPTION πŸ”₯

So this function queries the device for ice_ring_container-specific ITR values. Why per ice_ring_container? Because each q_vector can have 1 or more rings, and all of said ring(s) will have the same ITR values β€” that's the whole rule, periodt. πŸ’…

Returns 0 on success, negative otherwise. Simple as that, no cap. 🌈

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/net/ethernet/intel/ice/ice_ethtool.c

okay the see-also squad is huge, but every single one is here because we do not skip details:


okay that's the whole page, bestie. This manual entry comes from ./drivers/net/ethernet/intel/ice, dated October 2026, and it's the ice_get_rc_coalesce(9) page. byeee, stay slay πŸ’…πŸ’–

πŸ“¦ where this page comes from