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 of max_nb_rx πŸŽ€
  • rte_event_eth_adapter_create_with_params() β€” also configures the adapter with the default value of max_nb_rx πŸ’«
  • rte_event_eth_rx_adapter_create_ext() β€” this one lets you provide the value, by configuring the adapter with your user-provided max_nb_rx through the rte_event_eth_rx_adapter_conf::max_nb_rx parameter πŸ”₯
  • rte_event_eth_rx_adapter_runtime_params_set() β€” this is the glow-up button: it lets you re-configure max_nb_rx during 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