rte_port_eventdev.h(3)

💖 rte_port_eventdev.h — Library Functions Manual, section 3 💖

okay bestie, sit down, hydrate, and let's talk about rte_port_eventdev.h — it's a DPDK header, it lives in section 3 of the manual (the library-functions girlies), and it's honestly giving backstage-pass energy for the eventdev port world. 🎀

---

✨ NAME ✨

rte_port_eventdev.h — that's it, that's the name, no notes. 👑

---

🦋 SYNOPSIS 🦋

Pull it in like this, exactly like this:

#include <stdint.h>
#include <rte_eventdev.h>
#include 'rte_port.h'

(and yes, the single quotes around rte_port.h are literally what's in the source, don't come for me 😭)

🌸 Data Structures

Three little structs, all iconic, all in their own lane:

• struct rte_port_eventdev_reader_params
• struct rte_port_eventdev_writer_params
• struct rte_port_eventdev_writer_nodrop_params

🌈 Variables

And three exported ops bundles, serving looks:

• struct rte_port_in_ops rte_port_eventdev_reader_ops
• struct rte_port_out_ops rte_port_eventdev_writer_ops
• struct rte_port_out_ops rte_port_eventdev_writer_nodrop_ops

---

🧚 Detailed Description 🧚

RTE Port Eventdev Interface — say it with your chest. 💅

So the whole vibe here is: you already have an eventdev interface pre-initialized, and these ports just vibe on top of it. Two flavours, and they're both main characters:

• eventdev_reader — an input port built on top of a pre-initialized eventdev interface.
• eventdev_writer — an output port built on top of a pre-initialized eventdev interface.

<span>Definition in file rte_port_eventdev.h.</span> (iykyk, that's where the magic literally lives ✨)

ngl, the "pre-initialized" part is doing a lot of heavy lifting in that sentence. That eventdev interface? Already initialized. By you. Not by this header. Just so we're clear, bestie. 🙈

---

👑 Variable Documentation 👑

⭐ struct rte_port_in_ops rte_port_eventdev_reader_ops [extern]

Eventdev_reader port operations. 🫶 The input-side ops bundle, out here doing input-port things.

⭐ struct rte_port_out_ops rte_port_eventdev_writer_ops [extern]

Eventdev_writer port operations. 🌟 The output-side ops bundle, no-drop-free, just vibing.

⭐ struct rte_port_out_ops rte_port_eventdev_writer_nodrop_ops [extern]

Eventdev_writer_nodrop port operations. 🔥 The output-side ops bundle again, but the nodrop one — different name, different ops, we do not merge these, periodt.

---

💜 Author 💜

Generated automatically by Doxygen for DPDK from the source code. So nobody wrote this with their own two hands — the robot did it, and honestly? it ate. 🤖✨

---

<div style="text-align:center">🌸 🎀 🦋 🎀 🌸</div>

and that's the whole page, bestie! this bad boy is from DPDK, Version 25.11.3, and it's the rte_port_eventdev.h(3) manual page. go forth, build your ports, slay, and remember: pre-initialize that eventdev first. 💖💅🫶