STRUCT IWL_STATISTICS_RX_NTFY(9)

🎀 NAME 🎀

struct iwl_statistics_rx_ntfy — the RX statistics notification, bestie. It's the little struct that shows up with all your receive-side receipts ✨ (and this whole thing lives in the Kernel API Manual, iykyk 👑)

💖 SYNOPSIS 💖

struct iwl_statistics_rx_ntfy {
    struct iwl_statistics_ntfy_hdr hdr;
    __le32 rx_agg_mpdu_cnt;
    __le32 rx_agg_cnt;
    __le32 unsupported_mcs;
    __le32 bogus_cts;
    __le32 bogus_ack;
    __le32 rx_byte_count[MAC_INDEX_AUX];
    __le32 rx_packet_count[MAC_INDEX_AUX];
    __le32 missed_beacons;
    __le32 unresponded_rts;
    __le32 rxe_frame_limit_overrun;
    __le32 sent_ba_rsp_cnt;
    __le32 late_rx_handle;
    __le32 num_bt_kills;
    __le32 reserved;
 };

🌸 Members 🌸

• hdr — the general statistics header, the little intro before the main character speaks 🫶
• rx_agg_mpdu_cnt — aggregation frame count, and yes that means number of delimiters 🍓
• rx_agg_cnt — number of RX Aggregations, periodt 💅
• unsupported_mcs — number of PLCP headers rockin' a rate that DSP literally cannot support 😭
• bogus_cts — CTS received when nobody was expecting a CTS. rude tbh 💀
• bogus_ack — ACK received when nobody was expecting an ACK. also rude 🙈
• rx_byte_count — ??? (the header said it, not me, bestie — we simply do not know 🌫️)
• rx_packet_count — ??? (same vibe, the docs are mysterious 🧚)
• missed_beacons — ??? (beacons ghosted us and the docs ghosted us too 💔)
• unresponded_rts — un-responded RTS, and the reason is NAV not zero ⚠️
• rxe_frame_limit_overrun — RXE got a frame limit overrun, she's over capacity 😮‍💨
• sent_ba_rsp_cnt — BA response TX count, slay 🔥
• late_rx_handle — counts how many times the RX path got aborted due to a late entry ⏰
• num_bt_kills — ??? (the mystery member, truly giving main character energy 🌈)
• reserved — reserved. that's it. that's the whole description 🎀

🦋 SEE ALSO 🦋

Start with the kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/stats.h — that's home base, ok? 🏡

Then the whole friend group 👯‍♀️:

• struct mvm_statistics_rx_non_phy(9)
• struct mvm_statistics_load(9)
• enum iwl_statistics_notif_flags(9)
• enum iwl_statistics_cmd_flags(9)
• struct iwl_statistics_cmd(9)
• enum iwl_statistics_notify_type_id(9)
• enum iwl_statistics_cfg_flags(9)
• struct iwl_system_statistics_cmd(9)
• enum iwl_fw_statistics_type(9)
• struct iwl_statistics_ntfy_hdr(9)
• struct iwl_stats_ntfy_per_link(9)
• struct iwl_stats_ntfy_part1_per_link(9)
• struct iwl_stats_ntfy_per_mac(9)
• struct iwl_stats_ntfy_per_phy_v1(9)
• struct iwl_stats_ntfy_coex(9)
• struct iwl_stats_ntfy_per_phy(9)
• struct iwl_stats_ntfy_per_sta(9)
• struct iwl_system_statistics_notif_oper_v3(9)
• struct iwl_system_statistics_notif_oper(9)
• struct iwl_system_statistics_part1_notif_oper(9)
• struct iwl_system_statistics_end_notif(9)
• struct iwl_statistics_operational_ntfy(9)
• struct iwl_statistics_operational_ntfy_ver_14(9)
• struct iwl_statistics_phy_ntfy(9)
• struct iwl_statistics_mac_ntfy(9)
• struct iwl_statistics_tx_ntfy(9)
• struct iwl_statistics_duration_ntfy(9)
• struct iwl_statistics_he_ntfy(9)

ok so real talk: a bunch of those members are literally described as ??? in the source docs. I'm not out here inventing lore — if it says ???, it stays ???. no cap 🤐

this page came from ./drivers/net/wireless/intel/i... and it's dated October 2026 🌸 mwah, love u, go read ur stats structs 💖✨