RTE_EVENT_ETH_TX_ADAPTER_CONF(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

💖 NAME 💖

rte_event_eth_tx_adapter_conf — bestie, this is the config struct for your event ethernet TX adapter, and it's literally just two fields. That's it. That's the whole girl. 👑

It lives in the Library Functions Manual, section 3, so yes, we're in C-library-API territory, put your dev hat on. 🎀

✨ SYNOPSIS ✨

#include <rte_event_eth_tx_adapter.h>

🦋 Data Fields

  • uint8_t event_port_id
  • uint32_t max_nb_tx

🌸 Detailed Description 🌸

It's an Adapter configuration structure. Not a big dramatic monologue, just a lil struct whose whole job is holding your settings. 💅

See also

  • rte_event_eth_tx_adapter_create_ext
  • rte_event_eth_tx_adapter_conf_cb

Definition at line 96 of file rte_event_eth_tx_adapter.h.

🫶 Field Documentation 🫶

💜 uint8_t event_port_id

Event port identifier, okay? The adapter service function dequeues mbuf events from this port. So it's giving "this is the door where the events come out of", no cap. 🚪✨

See also

  • RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT

Definition at line 97 of file rte_event_eth_tx_adapter.h.

💜 uint32_t max_nb_tx

So here's the tea ☕: the adapter can return early if it has processed at least max_nb_tx mbufs.

⚠️ But bestie — this isn't treated as a requirement. Batching may cause the adapter to process more than max_nb_tx mbufs. So it's a soft vibe, not a hard limit. Don't come for it when it overshoots. 😭

Definition at line 102 of file rte_event_eth_tx_adapter.h.

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. She didn't write herself, she was born like this. 🤖💖

And that's the whole page, fr fr. This iconic little entry came to you from DPDK, Version 25.11.3, and it's rte_event_eth_tx_adapter_conf(3) signing off — go configure something slay. 💅✨🌈

📦 where this page comes from