MAX_NB_TX(3)
π rte_event_eth_tx_adapter_conf(3) β the manual page, but make it make sense
okay so bestie, this is rte_event_eth_tx_adapter_conf(3) from the DPDK Library Functions Manual, and it's literally just a lil struct that holds the config for the Ethernet TX adapter. it's giving "small but important", the backstage pass of the eventdev world π
β¨ NAME β¨
rte_event_eth_tx_adapter_conf β the adapter configuration structure, no cap π«Ά
πΈ SYNOPSIS πΈ
#include <rte_event_eth_tx_adapter.h>
π¦ Data Fields
uint8_t event_port_iduint32_t max_nb_tx
that's the whole squad, two fields, both iconic in their own way β¨
π Detailed Description π
it's the Adapter configuration structure β periodt. this is the struct you fill in to tell the TX adapter how to behave.
See also π
rte_event_eth_tx_adapter_create_extrte_event_eth_tx_adapter_conf_cb
Definition at line 96 of file rte_event_eth_tx_adapter.h. so if you're lost in the header, that's exactly where it lives π
π§ Field Documentation π§
π uint8_t event_port_id
the Event port identifier β the adapter's service function dequeues mbuf events from this port. it's basically the adapter's assigned seat in the group chat, lowkey. πͺ
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
okay so here's the tea: the adapter can return early if it has processed at least max_nb_tx mbufs. but β and this is the important part β it isn't treated as a requirement; batching may cause the adapter to process more than max_nb_tx mbufs. so it's a vibe, not a hard limit π don't come for it when the count overshoots, that's just batching doing its thing.
Definition at line 102 of file rte_event_eth_tx_adapter.h.
π Author π
Generated automatically by Doxygen for DPDK from the source code. so nobody hand-wrote this, the robots ate and left no crumbs π€β¨
ngl bestie, the thing to remember:event_port_id= where your events come from,max_nb_tx= a soft lil "you can stop around here" that batching is fully allowed to ignore. that's the whole vibe check π
and that's the page!! sign-off time: this was DPDK, Version 26.03.0, page rte_event_...dapter_conf(3) β mwah, go slay your eventdev config π
π
π¦ where this page comes from
- nixos 26.05: dpdk 26.03
- nixpkgs unstable: dpdk 26.03
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms