RTE_EVENT_ETH_RX_ADAPTER_RUNTIME_PARAMS(3)
π rte_event_eth_rx_adapter_runtime_params β the runtime glow-up struct π
okay bestie, so this is a data field page from the DPDK Library Functions Manual, section 3 π«Ά β it's the little struct that holds the runtime config for your event ethernet RX adapter. no cap, it's short, it's cute, let's go β¨
πΈ NAME πΈ
rte_event_eth_rx_adapter_runtime_params β the struct that carries the runtime configuration parameters for the adapter, periodt π
β¨ SYNOPSIS β¨
#include <rte_event_eth_rx_adapter.h>
π Data Fields π
uint32_t max_nb_rx
uint32_t rsvd[15]
π¦ DETAILED DESCRIPTION π¦
Adapter runtime configuration parameters π«Ά. That's the whole vibe β it's the bag of knobs you hand over when you wanna tweak how the adapter behaves while it's already running, not just at creation time.
It lives at Definition at line 311 of file rte_event_eth_rx_adapter.h β yes, we're citing our sources, we're academic like that πβ¨
π FIELD DOCUMENTATION π
uint32_t max_nb_rx π
So here's the tea: the adapter is allowed to return early if it's already processed at least max_nb_rx mbufs. But β and this is important, bestie β that is not treated as a requirement. Batching is out here doing its own thing, so the adapter may absolutely process more than max_nb_rx mbufs. It's giving "soft suggestion, not a vibe-enforced limit" π
Now, who sets this? Buckle up, there's a whole friend group:
rte_event_eth_rx_adapter_create()β configures the adapter with the default value ofmax_nb_rxπrte_event_eth_adapter_create_with_params()β also configures the adapter with the default value ofmax_nb_rxπ«rte_event_eth_rx_adapter_create_ext()β this one lets you provide the value, by configuring the adapter with your user-providedmax_nb_rxthrough therte_event_eth_rx_adapter_conf::max_nb_rxparameter π₯rte_event_eth_rx_adapter_runtime_params_set()β this is the glow-up button: it lets you re-configuremax_nb_rxduring runtime, i.e. after you've added at least one queue π
β οΈ heads up: this field is valid for the devices without RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT capability. if your device has that cap, this ain't for you, sorry babes π
Definition at line 312 of file rte_event_eth_rx_adapter.h.
uint32_t rsvd[15] π§
Reserved fields for future use π β aka the "we're saving seats for the next era, don't touch" corner. Don't poke at these, bestie, they're not yours yet π
Definition at line 329 of file rte_event_eth_rx_adapter.h.
π AUTHOR π
Generated automatically by Doxygen for DPDK, straight from the source code π€β¨ (yes, even the docs get auto-generated, we love a machine-made icon)
anyway that's the whole page, short and slay π this was DPDK, Version 25.11.3, living in the Library Functions Manual section 3, and honestly? iconic. go configure responsibly, bestie π«Άππ
π¦ where this page comes from
- ubuntu resolute: dpdk-doc 25.11.3-0ubuntu0.26.04.1 Β· BSD-3-Clause
- ubuntu stonking: dpdk-doc 25.11.3-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms