MBUF_PRIV_SIZE(3)

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

πŸ’… NAME πŸ’…

rte_pktmbuf_pool_private β€” bestie, this is a struct, and it's the little private-data bestie that hangs out in a pktmbuf pool ✨ (this page lives in the Library Functions Manual, iykyk)


✨ 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. This is the private data you get when you're dealing with a pktmbuf pool, periodt.

It's a structure that holds some pktmbuf_pool-specific data β€” and the way it works is those bits get appended after the mempool structure, like, inside the private data 🫢

The definition lives at line 301 of file rte_mbuf.h. Not me knowing the exact line number, but go off πŸ’…


πŸ¦‹ FIELD DOCUMENTATION πŸ¦‹

uint16_t mbuf_data_room_size

The size of the data space inside each mbuf. That's the room your data actually gets to vibe in πŸ’–

Definition at line 302 of file rte_mbuf.h.

uint16_t mbuf_priv_size

The size of the private area in each mbuf. Yes it's a different thing from the data room, don't come for me πŸ™ˆ

Definition at line 303 of file rte_mbuf.h.

uint32_t flags

Reserved for future use. So like… it's literally just sitting there being iconic and doing nothing yet πŸ‘‘

Definition at line 304 of file rte_mbuf.h.


πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. No cap, a robot wrote this, and honestly it ate πŸ’€


Heads up bestie: this whole page was auto-generated by Doxygen, so the "author" is a script, not a person. The facts above are the facts β€” the vibes are mine 🧚

And that's the whole page, mwah πŸ’‹ β€” with love from the DPDK docs, Version 26.03.0, brought to you by rte_pktmbuf_pool_private(3). See you in the next manpage, bestie! πŸŽ€βœ¨

πŸ“¦ where this page comes from