rte_ring_headtail(3)

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

πŸ’« NAME πŸ’«

rte_ring_headtail β€” okay bestie, that's the whole name, and this is the rte_ring_headtail(3) page from the Library Functions Manual. We're talking structures that hold head/tail values and other metadata, and it's giving very specific-ring-core energy. πŸŽ€


🌸 SYNOPSIS 🌸

Include this header and you get these public member functions, exactly like this:

#include <rte_ring_core.h>

   Public Member Functions
       volatile (uint32_t) head
       volatile (uint32_t) tail

πŸ¦‹ Detailed Description πŸ¦‹

Okay so picture structures to hold a pair of head/tail values and other metadata. Depending on sync_type, the format of that structure might be different, but the offset for sync_type and tail values should remain the same. No cap, that's the whole description. 🫢

Definition at line 65 of file rte_ring_core.h.


✨ Member Function Documentation ✨

  • volatile (uint32_t ) β€” prod/consumer head. πŸ’…
  • volatile (uint32_t ) β€” prod/consumer tail. πŸ’…

πŸŽ€ Field Documentation πŸŽ€

  • enum rte_ring_sync_type sync_type β€” sync type of prod/cons. Definition at line 70 of file rte_ring_core.h. ⭐
  • uint32_t single β€” deprecated - True if single prod/cons. Definition at line 72 of file rte_ring_core.h. 🚨
Heads up bestie: single is literally marked deprecated, so don't treat it like main character energy. The page says: deprecated - True if single prod/cons.

πŸ’œ Author πŸ’œ

Generated automatically by Doxygen for DPDK from the source code. 🫑


πŸ’– cute lil sign-off: this page is from DPDK, Version 26.03.0 β€” generated automatically by Doxygen for DPDK from the source code. The footer doesn't list a date on this one, so I'm not inventing one, bestie. Bye! πŸ’…βœ¨

πŸ“¦ where this page comes from