STRUCT ETHTOOL_RMON_STATS(9)

💅 struct ethtool_rmon_stats(9) — like, the RMON stats manual, bestie

okay so this is a page from the Kernel API Manual and it's all about struct ethtool_rmon_stats — which is literally just selected RMON (RFC 2819) statistics ✨ no cap, that's the whole name.

---

🌸 NAME 🌸

struct ethtool_rmon_stats — selected RMON (RFC 2819) statistics 🎀

---

✨ SYNOPSIS ✨

here's the whole struct, bestie, look at it, it's giving structured data realness:

struct ethtool_rmon_stats {
    enum ethtool_mac_stats_src src;
    struct {
      u64 undersize_pkts;
      u64 oversize_pkts;
      u64 fragments;
      u64 jabbers;
      u64 hist[ETHTOOL_RMON_HIST_MAX];
      u64 hist_tx[ETHTOOL_RMON_HIST_MAX];
    };
 };

---

🦋 Members 🦋

okay so let's go member by member, i got you:

• src — this is the input field that says whether the stats should be queried from the eMAC or the pMAC (but only if the MM layer is supported, iykyk). Otherwise it's to be ignored. straight up, don't think about it.
• {unnamed_struct} — it's anonymous. that's it. that's the whole vibe. 🙈
• undersize_pkts — equivalent to etherStatsUndersizePkts from the RFC. 💖
• oversize_pkts — equivalent to etherStatsOversizePkts from the RFC. 💖
• fragments — equivalent to etherStatsFragments from the RFC. 💖
• jabbers — equivalent to etherStatsJabbers from the RFC. (yes, jabbers. iconic name ngl.) 💖
• hist — packet counter for the packet length buckets, like etherStatsPkts128to255Octets from the RFC, fr fr. ⭐
• hist_tx — Tx counters in a similar form to hist, but not defined in the RFC, so that's a little freestyle moment of its own. 💅

---

🌈 Description 🌈

so this struct is a selection of RMON (RFC 2819) statistics which are not exposed via different APIs — mainly the packet-length-based counters, which is honestly the main character of the whole thing. 👑

and here's the messy part: unfortunately, different designs choose different buckets beyond the 1024B mark (jumbo frame teritory — yes that's how it's spelled in the source, we're keeping it, no editing the lore 🫶), so the definition of the bucket ranges is left to the driver. like, driver's choice. driver's vibe check. driver's problem.

careful bestie: because the bucket ranges are driver-defined past 1024B, don't go assuming they're the same across hardware. that's not me being dramatic, that's just the manual. 💀

---

👑 SEE ALSO 👑

the whole extended friend group, no one left behind:

• Kernel file ./include/linux/ethtool.h
• enum ethtool_phys_id_state(9)
• struct kernel_ethtool_ringparam(9)
• enum ethtool_supported_ring_param(9)
• ethtool_rxfh_indir_default(9)
• struct ethtool_rxfh_context(9)
• ethtool_link_ksettings_zero_link_mode(9)
• ethtool_link_ksettings_add_link_mode(9)
• ethtool_link_ksettings_del_link_mode(9)
• ethtool_link_ksettings_test_link_mode(9)
• ethtool_intersect_link_masks(9)
• struct ethtool_phy_stats(9)
• struct ethtool_pause_stats(9)
• struct ethtool_fec_hist_range(9)
• struct ethtool_fec_stats(9)
• struct ethtool_rmon_hist_range(9)
• struct ethtool_ts_stats(9)
• struct ethtool_module_eeprom(9)
• struct ethtool_module_power_mode_params(9)
• struct ethtool_mm_state(9)
• struct ethtool_mm_cfg(9)
• struct ethtool_mm_stats(9)
• struct ethtool_mmsv_ops(9)
• struct ethtool_mmsv(9)
• struct ethtool_rxfh_param(9)
• struct ethtool_rxfh_fields(9)
• struct kernel_ethtool_ts_info(9)
• struct ethtool_ops(9)
• struct ethtool_netdev_state(9)
• struct ethtool_phy_ops(9)
• ethtool_set_ethtool_phy_ops(9)
• ethtool_params_from_link_mode(9)
• ethtool_get_phc_vclocks(9)
• ethtool_mm_frag_size_add_to_min(9)
• ethtool_mm_frag_size_min_to_add(9)
• ethtool_get_ts_info_by_layer(9)
• ethtool_sprintf(9)
• ethtool_puts(9)
• ethtool_cpy(9)

---

🌸 okay that's the page, hope you ate it up 🌸

this one lives in ./include/linux and it's dated October 2026, and the header up top is struct ethtool_rmon_stats(9) in case you forgot already lol. bye bestie, go read your ethtool headers 💖🎀🦋