rte_event_...apter_conf(3)

πŸ’– NAME πŸ’–

rte_event_dma_adapter_conf β€” bestie this is the whole vibe of the page, it's a struct name and nothing else, slay


✨ SYNOPSIS ✨

#include <rte_event_dma_adapter.h>

πŸŽ€ Data Fields

  • uint32_t max_nb

🌸 DETAILED DESCRIPTION 🌸

Okay so listen. This is the adapter configuration structure that the adapter configuration callback function is expected to fill out. That's the whole job. It gets handed to you, you fill it in, everybody's happy. πŸ’…

see also πŸ‘€

  • rte_event_dma_adapter_conf_cb
Definition at line 182 of file rte_event_dma_adapter.h.

πŸ¦‹ FIELD DOCUMENTATION πŸ¦‹

uint32_t max_nb

ngl the doc literally starts with a < β€” that's Doxygen being quirky, not me. Here's the tea:

  • < Event port identifier β€” the adapter enqueues events to this port and dequeues DMA request events in RTE_EVENT_DMA_ADAPTER_OP_FORWARD mode. 🫢
  • The adapter can return early if it has processed at least max_nb DMA ops.
  • This isn't treated as a requirement β€” batching may cause the adapter to process more than max_nb DMA ops. So it's giving "soft suggestion," not "hard limit," fr fr.
Definition at line 188 of file rte_event_dma_adapter.h.

πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. Not a human, not a girlie, just a doc generator doing its little thing. ✨


πŸ’– okay that's the whole page bestie!! this one came out of the DPDK house, Version 25.11.3, and the lovely manual name it lives under is Library Functions Manual, section 3. bye ily, read your manpages, hydrate!! πŸŽ€πŸ¦‹πŸŒΈπŸ’…

πŸ“¦ where this page comes from