rte_event_queue_conf(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💅 rte_event_queue_conf(3)

okay so bestie, welcome to the Library Functions Manual ✨ this one is literally all about rte_event_queue_conf — the event queue configuration struct. she's giving main character energy and you're gonna be obsessed 🎀

🌸 NAME

rte_event_queue_conf — the event queue configuration structure, periodt 💖

✨ SYNOPSIS

#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 💅 she's the blueprint, the icon, the moment.

Definition at line 911 of file rte_eventdev.h.

🎀 Field Documentation

💜 uint32_t nb_atomic_flows

The maximum number of active flows this queue can track at any given time. no cap, that's her whole job.

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(). respect the range bestie 😤

If the queue is not configured for atomic scheduling this value is ignored. she's literally off duty, leave her alone 🙈

Definition at line 912 of file rte_eventdev.h.

🌈 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 no events will be returned from dequeue until one or more entries are freed up/released. like bestie, the buffer is FULL, nobody's getting out until somebody leaves, it's giving club at capacity 💀

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().

If the queue is not configured for ordered scheduling, then this value is ignored. not her era, moving on 🦋

Definition at line 925 of file rte_eventdev.h.

🍓 uint32_t event_queue_cfg

Queue cfg flags (EVENT_QUEUE_CFG_) — the little flag collection that tells the queue who she is 💅

Definition at line 943 of file rte_eventdev.h.

🧚 uint8_t schedule_type

Queue schedule type (RTE_SCHED_TYPE_*). the personality picker fr fr.

Valid when RTE_EVENT_QUEUE_CFG_ALL_TYPES flag is not set in event_queue_cfg.

If the RTE_EVENT_QUEUE_CFG_ALL_TYPES flag is set, then this field is ignored. she said "I contain multitudes", so the single type field gets benched 🙈

See also

  • RTE_SCHED_TYPE_ORDERED
  • RTE_SCHED_TYPE_ATOMIC
  • RTE_SCHED_TYPE_PARALLEL
Definition at line 945 of file rte_eventdev.h.

⭐ uint8_t priority

Priority for this event queue relative to other event queues. who gets served first, iykyk 👑

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. she'll translate your vibe into something the hardware actually understands, slay ✨

Valid when the device has RTE_EVENT_DEV_CAP_QUEUE_QOS capability, ignored otherwise. no QoS? then this field is literally just vibes and nothing else 🫶

Definition at line 955 of file rte_eventdev.h.

🔥 uint8_t weight

Weight of the event queue relative to other event queues. how much attention she gets in the group chat, basically 💖

The requested weight should be in the range of [RTE_EVENT_QUEUE_WEIGHT_HIGHEST, RTE_EVENT_QUEUE_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, ignored otherwise. same deal, no cap.

Definition at line 966 of file rte_eventdev.h.

🌸 uint8_t affinity

Affinity of the event queue relative to other event queues. which queues she's closest to, bestie dynamics fr fr 🥰

The requested affinity should be in the range of [RTE_EVENT_QUEUE_AFFINITY_HIGHEST, RTE_EVENT_QUEUE_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, ignored otherwise. (yes, again. QoS is the whole personality here 😭)

Definition at line 977 of file rte_eventdev.h.

💀 Author

Generated automatically by Doxygen for DPDK from the source code. not me being auto-generated and still having more personality than half the codebase 💅

okay that's the whole page bestie, you ate that 🍓✨ stay hydrated, respect your ranges, and remember: no QoS capability means priority, weight, and affinity are all just ignored. iconic behavior honestly.

big kiss from DPDK, Version 26.03.0 🎀💜🦋

📦 where this page comes from