RTE_PKTMBUF_POOL_PRIVATE(3)

✨ NAME ✨

rte_pktmbuf_pool_private β€” bestie, this is the little secret-snack struct that hangs out behind your pktmbuf pool πŸŽ€


🌸 SYNOPSIS 🌸

#include <rte_mbuf.h>

πŸ’… Data Fields

  • uint16_t mbuf_data_room_size
  • uint16_t mbuf_priv_size
  • uint32_t flags

πŸ¦‹ Detailed Description πŸ¦‹

okay so, private data in case of pktmbuf pool πŸ’–

it's a structure, right, and it holds some pktmbuf_pool-specific data β€” the kind of stuff that gets appended after the mempool structure (like, in the private data). that's literally its whole job. it's giving backstage pass energy, no cap.

Definition at line 301 of file rte_mbuf.h. πŸ‘‘

πŸŽ€ Field Documentation πŸŽ€

uint16_t mbuf_data_room_size

Size of data space in each mbuf. so like, how much room each mbuf's data area gets to vibe in ✨

Definition at line 302 of file rte_mbuf.h.

uint16_t mbuf_priv_size

Size of private area in each mbuf β€” the personal-space allocation, we love a boundary-setting queen πŸ™ˆ

Definition at line 303 of file rte_mbuf.h.

uint32_t flags

reserved for future use. yeah bestie it's just sitting there, a placeholder, manifesting its future era, we don't ask questions πŸ’€

Definition at line 304 of file rte_mbuf.h.


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. not a human author, just doxygen doing its little automated thing, and honestly? iconic ⭐


so yeah, that's the whole page, rte_pktmbuf_pool_private(3) from DPDK Version 25.11.3 β€” Doxygen-generated and everything, periodt πŸ’œπŸ«Ά go read rte_mbuf.h if you want the receipts, mwah 🧚

πŸ“¦ where this page comes from