rte_mtr_stats(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

🎀 NAME 🎀

rte_mtr_stats is the main character of this page, bestie — a DPDK Library Functions Manual entry all about Statistics counters. 💅✨

🌸 SYNOPSIS 🌸

#include <rte_mtr.h>

🧸 Data Fields 🧸

  • uint64_t n_pkts [RTE_COLORS] — how many packets passed the policer, counted per color. 🌈
  • uint64_t n_bytes [RTE_COLORS] — how many bytes passed the policer, counted per color. 💖
  • uint64_t n_pkts_dropped — how many packets the policer dropped. 💀
  • uint64_t n_bytes_dropped — the docs say this is the number of bytes passed by the policer. Yes, literally. Keep reading, bestie. 🙈

✨ Detailed Description ✨

These are Statistics counters — the receipts, the numbers, the whole vibe check of your policer stats. 🫶

Definition at line 90 of file rte_mtr.h.

🔥 Field Documentation 🔥

uint64_t n_pkts[RTE_COLORS]

Number of packets passed by the policer, per color. That [RTE_COLORS] is doing the “one counter per color” thing, iykyk. 🌈

Definition at line 92 of file rte_mtr.h.

uint64_t n_bytes[RTE_COLORS]

Number of bytes passed by the policer, per color. Byte girl summer. 💖

Definition at line 95 of file rte_mtr.h.

uint64_t n_pkts_dropped

Number of packets dropped by the policer. The “oops, that packet didn’t make it” counter. 💀

Definition at line 98 of file rte_mtr.h.

uint64_t n_bytes_dropped

Number of bytes passed by the policer. 🫠 Yes, bestie — that is literally what the docs say here: passed, even though the field name is n_bytes_dropped. I’m not fixing it, I’m just reporting it. 🙈

Definition at line 101 of file rte_mtr.h.

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. So the robots get the credit, not me. 🤖💅

Sign-off: this DPDK page is Version 26.03.0, rte_mtr_stats(3), and the footer has no date, so we’re closing with vibes only. Byeee! 💖✨🦋

📦 where this page comes from