ice_fetch_tx_ring_stats(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ice_fetch_tx_ring_stats β€” Kernel API Manual ✨

okay so bestie, we're in section 9 of the Kernel API Manual today, and the star of the show is ice_fetch_tx_ring_stats β€” say it with me, it's giving "one job, does it well" energy πŸ’…


🌸 NAME 🌸

ice_fetch_tx_ring_stats β€” fetch Tx ring packet and byte counters πŸŽ€

Like, it reaches into a transmit ring and scoops out the counters. That's the whole vibe. No cap.


✨ SYNOPSIS ✨

void ice_fetch_tx_ring_stats (const struct ice_tx_ring *ring , u64 *pkts
, u64 *bytes );

Notice the void β€” it returns absolutely nothing because it's not about giving you answers, it's about filling in your pointers. Main character energy, honestly πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ring β€” the ring to update, passed as const struct ice_tx_ring *. It's the Tx ring we're snooping on 🧚
  • pkts β€” a u64 *, and it gets the number of processed packets πŸ“¦
  • bytes β€” also a u64 *, and it gets the number of processed bytes πŸ“
⭐ bestie reminder: pkts and bytes are pointers, so this function writes through them. You hand it somewhere to put the numbers, it puts the numbers there. That's the entire deal fr fr.

🌈 SEE ALSO 🌈

okay so first up is the kernel file it lives near:

  • ./drivers/net/ethernet/intel/ice/ice_lib.c

and then β€” no exaggeration β€” the entire friend group shows up. Every single one of these, exactly as written, because we do not skip people's names in this house πŸ’–

πŸ’€ one hundred and six cross-refs and not a single one skipped. that's the level of commitment we're on. iykyk 🫢

and that's the whole page, bestie β€” short, sweet, and deeply iconic ✨ this one's coming at you from ./drivers/net/ethernet/intel/ice, dated October 2026, and yes it's still ice_fetch_tx_ring_stats(9) at the end of the day πŸŽ€ bye mwah πŸ’œ

πŸ“¦ where this page comes from