MAX_NB_RX(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’… MAX_NB_RX(3) β€” like, the whole rte_event_...dapter_conf(3) moment ✨

Okay bestie, so this page is officially titled MAX_NB_RX(3), but the manual name it's filed under is rte_event_...dapter_conf(3) β€” yes that's the truncated lil nickname, that's how it shows up, no cap 🫢. It's a Library Functions Manual page and it's literally all about one struct. Let's get into it.


🌸 NAME 🌸

rte_event_eth_rx_adapter β€” that's the whole name, that's the vibe, that's the function-adjacent thing this page documents πŸ’–


✨ SYNOPSIS ✨

#include <rte_event_eth_rx_adapter.h>

πŸŽ€ Data Fields πŸŽ€

uint8_t event_port_id
uint32_t max_nb_rx

Two fields. That's it. That's the struct. Iconic minimalism honestly πŸ‘‘


πŸ¦‹ Detailed Description πŸ¦‹

So this is the adapter configuration structure that the adapter configuration callback function is expected to fill out. Like, the callback gets handed this thing and it's supposed to do its little job and populate it. That's the whole assignment πŸ“

See also β€” rte_event_eth_rx_adapter_conf_cb (go read that one after this, iykyk)

Definition at line 118 of file rte_event_eth_rx_adapter.h. ✨


πŸ”₯ Field Documentation πŸ”₯

πŸ’œ uint8_t event_port_id

This is the event port identifier β€” the adapter enqueues mbuf events to this port. So like, that's where the events go. That port. Right there. Enqueued. 🎯

Definition at line 119 of file rte_event_eth_rx_adapter.h.

πŸ“ uint32_t max_nb_rx

Okay so here's the tea β˜•: the adapter can return early if it has processed at least max_nb_rx mbufs.

But β€” and this is the important part, don't skip it β€” this isn't treated as a requirement. Batching may cause the adapter to process more than max_nb_rx mbufs. So it's a soft "yeah that's probably enough" kind of number, not a hard cap. Don't come for the adapter when it overshoots, that's just batching being batching πŸ™ˆ

Definition at line 123 of file rte_event_eth_rx_adapter.h.


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. So nobody actually wrote this by hand, it was literally generated β€” we stan an automated queen πŸ€–πŸ’…


Okay that's the whole page bestie, you ate that reading, fr fr πŸŒˆπŸ¦‹

<div align="center">β€” cute lil sign-off β€”</div>

This was DPDK, Version 26.03.0, and the page date/footer says it's rte_event_...dapter_conf(3) under the Library Functions Manual. Mwah πŸ’‹ πŸŽ€β­

πŸ“¦ where this page comes from