rte_event_...pter_stats(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

✨ NAME ✨

rte_event_vector_adapter_stats β€” bestie, this is the vector adapter statistics structure, like, the whole vibe report card for your vector adapter πŸ’… (also it's a page from the DPDK Library Functions Manual, iykyk)


🌸 SYNOPSIS 🌸

#include <rte_event_vector_adapter.h>

πŸŽ€ Data Fields

  • uint64_t vectorized
  • uint64_t vectors_timedout
  • uint64_t vectors_flushed
  • uint64_t alloc_failures

πŸ¦‹ Detailed Description

So this struct lowkey is the Vector adapter statistics structure 🫢 β€” it's where all the numbers about your vector adapter live. No cap.

Fr fr, it's defined at line 207 of the file rte_event_vector_adapter.h, so that's the main character's address πŸ“

πŸ’– Field Documentation πŸ’–

uint64_t vectorized

The count of events that got vectorized β€” literally how many events made it into vectors ✨

Defined at line 208 of file rte_event_vector_adapter.h.

uint64_t vectors_timedout

The number of timeouts that occurred 😭 (yes, they happened, and this field is keeping receipts)

Defined at line 210 of file rte_event_vector_adapter.h.

uint64_t vectors_flushed

How many vectors got flushed 🚽✨ β€” dramatic but necessary

Defined at line 212 of file rte_event_vector_adapter.h.

uint64_t alloc_failures

The number of vector allocation failures πŸ’€ β€” the not-so-slaying moments, counted one by one

Defined at line 214 of file rte_event_vector_adapter.h.


πŸ‘‘ Author

Generated automatically by Doxygen for DPDK from the source code. 🧚 Not me being auto-generated, she's iconic like that πŸ™ˆ


Okay bestie, that's the whole page β€” brought to you by DPDK, Version 26.03.0, and this little manpage is dated the same. Go forth and read your stats πŸ’œ

πŸ“¦ where this page comes from