On Fri, Feb 10, 2023 at 7:03 PM Naga Harish K S V
<s.v.naga.haris...@intel.com> wrote:
>
> The adapter configuration parameters defined in the
> struct rte_event_eth_rx_adapter_runtime_params can be configured
> and retrieved using rte_event_eth_rx_adapter_runtime_params_set and
rte_event_eth_rx_adapter_runtime_params_set()
> rte_event_eth_tx_adapter_runtime_params_get respectively.
rte_event_eth_tx_adapter_runtime_params_get()
>
> Signed-off-by: Naga Harish K S V <s.v.naga.haris...@intel.com>
> ---
> +/**
> + * Adapter runtime configuration parameters
> + */
> +struct rte_event_eth_rx_adapter_runtime_params {
> + uint32_t max_nb_rx;
> + /**< The adapter can return early if it has processed at least
> + * max_nb_rx mbufs. This isn't treated as a requirement; batching may
> + * cause the adapter to process more than max_nb_rx mbufs.
> + *
> + * rte_event_eth_rx_adapter_create() or
> + * rte_event_eth_adapter_create_with_params() configures the
> + * adapter with default value of maximum packets processed per
> + * iteration to 128.
> + * rte_event_eth_rx_adapter_runtime_params_set() allows to
> re-configure
> + * maximum packets processed per iteration. This is alternative to
> using
> + * rte_event_eth_rx_adapter_create_ext() with parameter
> + * rte_event_eth_rx_adapter_conf::max_nb_rx
> + *
> + * This is valid for service based SW adapter only
This is valid for the devices without
RTE_EVENT_ETH_RX_ADAPTER_CAP_INTERNAL_PORT capability.
