ixgbe_update_rx_ring_stats(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ixgbe_update_rx_ring_stats — the Kernel API Manual glow-up

okay so real talk, bestie: this little function lives in the Kernel API Manual (that's the manual name, and yes she's serving kernel-doc energy 👑). Her whole personality? Updating the counters for one specific Rx ring. That's it. That's the girl. No cap, sometimes the most iconic thing you can do is just increment a number the right way. ✨

🌸 NAME

ixgbe_update_rx_ring_stats — update Rx ring specific counters 💖

like, specifically rx ring counters. not all the counters. hers. periodt.

🦋 SYNOPSIS

void ixgbe_update_rx_ring_stats (struct ixgbe_ring *rx_ring , struct
       ixgbe_q_vector *q_vector , u64 pkts , u64 bytes );

returns void, so nobody's gonna come back at you with an error code. she just does the thing and dips 🫶

🎀 ARGUMENTS

  • rx_ring — the ring to update 🌈 like, the actual star of the show, the struct ixgbe_ring receiving the new stats
  • q_vector — the queue vector that ring belongs to 🧚 her plus-one, the struct ixgbe_q_vector she's associated with
  • pkts — number of processed packets 📦 a u64, so go ahead and count big, she can hold it
  • bytes — number of processed bytes 🍓 also a u64, also not scared of a big number, we love a size-queen data type
lowkey the whole flow is: you hand her a ring, its q_vector, and the packet + byte counts you already tallied, and she makes the stats happen. no drama, no return value, no notes 💅

🔥 SEE ALSO

the friend group 💜 — and bestie there are so many of them, every single one gets their moment:

and that's the whole page, bestie 💀🦋 okay one last thing — the source line at the bottom is literally ./drivers/net/ethernet/intel/i... (yes, it's truncated, she's mysterious like that 🙈) and the date is October 2026, so mark your calendar and stan 💖✨🎀

📦 where this page comes from