DPDK 22.11.5
Data Fields
rte_event_queue_conf Struct Reference

#include <rte_eventdev.h>

Data Fields

uint32_t nb_atomic_flows
 
uint32_t nb_atomic_order_sequences
 
uint32_t event_queue_cfg
 
uint8_t schedule_type
 
uint8_t priority
 
uint8_t weight
 
uint8_t affinity
 

Detailed Description

Event queue configuration structure

Examples
examples/eventdev_pipeline/pipeline_worker_generic.c, examples/eventdev_pipeline/pipeline_worker_tx.c, examples/ipsec-secgw/event_helper.c, examples/l2fwd-event/l2fwd_event_generic.c, examples/l2fwd-event/l2fwd_event_internal_port.c, examples/l3fwd/l3fwd_event_generic.c, and examples/l3fwd/l3fwd_event_internal_port.c.

Definition at line 619 of file rte_eventdev.h.

Field Documentation

◆ nb_atomic_flows

uint32_t nb_atomic_flows

The maximum number of active flows this queue can track at any given time. If the queue is configured for atomic scheduling (by applying the RTE_EVENT_QUEUE_CFG_ALL_TYPES flag to event_queue_cfg or RTE_SCHED_TYPE_ATOMIC flag to schedule_type), then the value must be in the range of [1, nb_event_queue_flows], which was previously provided in rte_event_dev_configure().

Examples
examples/ipsec-secgw/event_helper.c, examples/l2fwd-event/l2fwd_event_generic.c, examples/l2fwd-event/l2fwd_event_internal_port.c, examples/l3fwd/l3fwd_event_generic.c, and examples/l3fwd/l3fwd_event_internal_port.c.

Definition at line 620 of file rte_eventdev.h.

◆ nb_atomic_order_sequences

uint32_t nb_atomic_order_sequences

The maximum number of outstanding events waiting to be reordered by this queue. In other words, the number of entries in this queue’s reorder buffer.When the number of events in the reorder buffer reaches to nb_atomic_order_sequences then the scheduler cannot schedule the events from this queue and invalid event will be returned from dequeue until one or more entries are freed up/released. If the queue is configured for ordered scheduling (by applying the RTE_EVENT_QUEUE_CFG_ALL_TYPES flag to event_queue_cfg or RTE_SCHED_TYPE_ORDERED flag to schedule_type), then the value must be in the range of [1, nb_event_queue_flows], which was previously supplied to rte_event_dev_configure().

Examples
examples/ipsec-secgw/event_helper.c, examples/l2fwd-event/l2fwd_event_internal_port.c, and examples/l3fwd/l3fwd_event_internal_port.c.

Definition at line 628 of file rte_eventdev.h.

◆ event_queue_cfg

uint32_t event_queue_cfg

◆ schedule_type

uint8_t schedule_type

◆ priority

uint8_t priority

Priority for this event queue relative to other event queues. The requested priority should in the range of [RTE_EVENT_DEV_PRIORITY_HIGHEST, RTE_EVENT_DEV_PRIORITY_LOWEST]. The implementation shall normalize the requested priority to event device supported priority value. Valid when the device has RTE_EVENT_DEV_CAP_QUEUE_QOS capability

Examples
examples/eventdev_pipeline/pipeline_worker_generic.c, examples/eventdev_pipeline/pipeline_worker_tx.c, examples/ipsec-secgw/event_helper.c, examples/l2fwd-event/l2fwd_event_generic.c, and examples/l3fwd/l3fwd_event_generic.c.

Definition at line 649 of file rte_eventdev.h.

◆ weight

uint8_t weight

Weight of the event queue relative to other event queues. The requested weight should be in the range of [RTE_EVENT_DEV_WEIGHT_HIGHEST, RTE_EVENT_DEV_WEIGHT_LOWEST]. The implementation shall normalize the requested weight to event device supported weight value. Valid when the device has RTE_EVENT_DEV_CAP_QUEUE_QOS capability.

Definition at line 657 of file rte_eventdev.h.

◆ affinity

uint8_t affinity

Affinity of the event queue relative to other event queues. The requested affinity should be in the range of [RTE_EVENT_DEV_AFFINITY_HIGHEST, RTE_EVENT_DEV_AFFINITY_LOWEST]. The implementation shall normalize the requested affinity to event device supported affinity value. Valid when the device has RTE_EVENT_DEV_CAP_QUEUE_QOS capability.

Definition at line 665 of file rte_eventdev.h.


The documentation for this struct was generated from the following file: