rte_swx_table_stats(3)

πŸ’– rte_swx_table_stats β€” a manual page, but make it cute πŸ’–

okay bestie, welcome to the rte_swx_table_stats(3) page from the Library Functions Manual πŸ’… she's a struct, she's iconic, and she's lowkey just a little bundle of counters, but we are going to give her the main character energy she deserves. no cap.


✨ NAME ✨

rte_swx_table_stats β€” literally the name, that's it, that's the whole name πŸŽ€


✨ SYNOPSIS ✨

so first things first, you gotta pull her in:

#include <rte_swx_ctl.h>

🌸 Data Fields 🌸

and inside her? these three fields. that's the whole squad:

  • uint64_t n_pkts_hit
  • uint64_t n_pkts_miss
  • uint64_t * n_pkts_action

✨ Detailed Description ✨

okay so what IS she? she's Table statistics. that's it, that's her whole job description fr fr. she holds the numbers about what your table has been up to.

she's defined at line 377 of the file rte_swx_ctl.h, if you ever need to go say hi in person 🫢


✨ Field Documentation ✨

okay now let's meet the girls one by one, we're doing intros πŸ¦‹

🌈 uint64_t n_pkts_hit

the number of packets with a lookup hit. that's the count of packets where the lookup actually found something β€” the slay outcome πŸ’…

she lives at line 379 of rte_swx_ctl.h.

🌈 uint64_t n_pkts_miss

the number of packets with a lookup miss. yeah so these are the ones that didn't find anything. it's giving sad but we still count them, everyone gets a number πŸ”₯

she lives at line 382 of rte_swx_ctl.h.

🌈 uint64_t* n_pkts_action

okay this one's the overachiever, pay attention πŸ“£

  • the number of packets (with either lookup hit or miss) per pipeline action.
  • it's described as an array of pipeline n_actions elements, indexed by the pipeline-level action_id.
  • and because of that indexing, this array has the same size for all the tables within the same pipeline. like, every table in that pipeline is matching, periodt. no size drama.

she lives at line 389 of rte_swx_ctl.h.


✨ Author ✨

Generated automatically by Doxygen for DPDK from the source code. so like, nobody hand-wrote this, the robot did it, and honestly? the robot ate πŸ’€βœ¨


okay bestie quick recap so you don't forget: three fields, n_pkts_hit, n_pkts_miss, and n_pkts_action, all about packets in your table, and the action one is per-pipeline-action indexed by action_id. that's the whole vibe check. go forth and count packets πŸŽ€

and that's the page bestie!! brought to you by DPDK, Version 25.11.3 β€” that's the whole footer, mwah, bye, love you, drink water, check your lookup hits πŸ’–πŸ’…πŸ¦‹βœ¨

πŸ“¦ where this page comes from