rte_node_mbuf_dynfield(3)

💅 rte_node_mbuf_dynfield — like, the whole vibe

okay bestie, quick housekeeping: this is a page from the Library Functions Manual, and the star of the show is rte_node_mbuf_dynfield. yes it's a mouthful, no we're not renaming it, periodt.

---

✨ NAME ✨

rte_node_mbuf_dynfield — bestie, that's literally it, that's the name 💖

---

🎀 SYNOPSIS 🎀

#include <rte_node_mbuf_dynfield.h>

🌸 Data Fields 🌸

• rte_node_mbuf_overload_fields_t overloadable_data

---

🦋 Detailed Description 🦋

so this is the rte_node specific mbuf dynamic field structure, aka [rte_node_mbuf_dynfield_t]. iconic, no notes.

the way that it holds two types of fields is honestly the whole plot:

1. Persistent fields — these are the fields that are preserved across nodes during a graph walk. they stay with you, ride or die 🫶
   • eg: rx/tx interface etc
2. Overloadable fields — these are fields which can be repurposed by two adjacent nodes. they're flexible like that, lowkey main character energy 🔥

Definition at line 71 of file rte_node_mbuf_dynfield.h — iykyk ✨

---

👑 Field Documentation 👑

⭐ rte_node_mbuf_overload_fields_t overloadable_data

Overloadable mbuf fields across the graph walk. Fields which can change. ngl, this is the "go with the flow" part of the struct 💫

Two adjacent nodes (producer, consumer) can use this memory region for sharing per-mbuf specific information. once the mbuf leaves a consumer node, this region can be repurposed by another sets of [producer, consumer] node. like a group chat that just keeps getting new members, fr fr.

in the fast path, this region can be accessed by rte_node_mbuf_overload_fields_get() — that's your entry point bestie, remember it 📌

Definition at line 92 of file rte_node_mbuf_dynfield.h — yes, another line number, we love documentation 💀

---

🌈 Author 🌈

Generated automatically by Doxygen for DPDK from the source code. no human author to thank, the robots ate and left no crumbs 🤖💅

---

and that's the page!! mwah 💖 — this cutie was brought to you by DPDK, Version 26.03.0, dated right there in the footer of the original page, and yes we're closing it out with a little sign-off instead of copying that footer line verbatim. slay, go forth and read your headers 🎀🦋✨