rte_event_dev_info(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

✨ rte_event_dev_info ✨

Okay bestie, so this is a page out of the DPDK library manual (the Library Functions Manual one, you know the vibe), and it's all about this one little struct called rte_event_dev_info — literally the whole personality profile of an event device. Every field is a lil fact about what your device can and can't do. Let's get into it 💅

#include <rte_eventdev.h>

🌸 Data Fields 🌸

  • const char * driver_name — the driver's name, bestie. That's it, that's the field.
  • struct rte_device * dev — the device info.
  • uint32_t min_dequeue_timeout_ns — the smallest global dequeue timeout (in ns) this device can handle.
  • uint32_t max_dequeue_timeout_ns — the biggest global dequeue timeout (in ns) this device can handle.
  • uint32_t dequeue_timeout_ns — the global dequeue timeout (in ns) that's actually configured for this device right now.
  • uint8_t max_event_queues — max event queues this device supports. Heads up tho: this count does not include any queues covered by max_single_link_event_port_queue_pairs.
  • uint32_t max_event_queue_flows — the max number of flows inside a single event queue that this device supports.
  • uint8_t max_event_queue_priority_levels — max number of event queue priority levels this device supports. Only valid when the device has the RTE_EVENT_DEV_CAP_QUEUE_QOS capability.
  • uint8_t max_event_priority_levels — max number of event priority levels this device supports. Only valid when the device has the RTE_EVENT_DEV_CAP_EVENT_QOS capability.
  • uint8_t max_event_ports — max event ports this device supports. And again, this count does not include any ports covered by max_single_link_event_port_queue_pairs.
  • uint8_t max_event_port_dequeue_depth — max number of events you can dequeue at a time from an event port on this device. If a device doesn't support burst dequeue (RTE_EVENT_DEV_CAP_BURST_MODE), it'll set this to 1.
  • uint32_t max_event_port_enqueue_depth — max number of events you can enqueue at a time to an event port on this device. If a device doesn't support burst enqueue (RTE_EVENT_DEV_CAP_BURST_MODE), it'll set this to 1.
  • uint8_t max_event_port_links — max number of queues that can be linked to a single event port on this device.
  • int32_t max_num_events — a closed system event dev has a cap on how many events it can juggle at once. The second the number of events tracked by the eventdev goes over this, any enqueues of NEW events will fail. An open system event dev has no limit and will just give you -1 for this.
  • uint32_t event_dev_cap — the event device capability flags (RTE_EVENT_DEV_CAP_*).
  • uint8_t max_single_link_event_port_queue_pairs — max number of event ports and queues this device supports that are optimized for (and only capable of) single-link configs. These ports and queues are not counted in max_event_ports or max_event_queues.
  • uint8_t max_profiles_per_port — max number of event queue link profiles per event port. A device that doesn't support multiple profiles will set this to 1.

💖 Detailed Description 💖

Event device information. That's the whole assignment, fr fr.

Definition at line 600 of file rte_eventdev.h.

🎀 Field Documentation 🎀

🦋 const char* driver_name

Event driver name.

Definition at line 601 of file rte_eventdev.h.

🦋 struct rte_device* dev

Device information.

Definition at line 602 of file rte_eventdev.h.

🦋 uint32_t min_dequeue_timeout_ns

Minimum global dequeue timeout(ns) supported by this device.

Definition at line 603 of file rte_eventdev.h.

🦋 uint32_t max_dequeue_timeout_ns

Maximum global dequeue timeout(ns) supported by this device.

Definition at line 605 of file rte_eventdev.h.

🦋 uint32_t dequeue_timeout_ns

Configured global dequeue timeout(ns) for this device.

Definition at line 607 of file rte_eventdev.h.

🦋 uint8_t max_event_queues

Maximum event queues supported by this device.

This count excludes any queues covered by max_single_link_event_port_queue_pairs.

Definition at line 609 of file rte_eventdev.h.

🦋 uint32_t max_event_queue_flows

Maximum number of flows within an event queue supported by this device.

Definition at line 614 of file rte_eventdev.h.

🦋 uint8_t max_event_queue_priority_levels

Maximum number of event queue priority levels supported by this device.

Valid when the device has RTE_EVENT_DEV_CAP_QUEUE_QOS capability.

The implementation shall normalize priority values specified between RTE_EVENT_DEV_PRIORITY_HIGHEST and RTE_EVENT_DEV_PRIORITY_LOWEST to map them internally to this range of priorities. [For devices supporting a power-of-2 number of priority levels, this normalization will be done via a right-shift operation, so only the top log2(max_levels) bits will be used by the event device.]

See also: rte_event_queue_conf.priority

Definition at line 616 of file rte_eventdev.h.

🦋 uint8_t max_event_priority_levels

Maximum number of event priority levels by this device.

Valid when the device has RTE_EVENT_DEV_CAP_EVENT_QOS capability.

The implementation shall normalize priority values specified between RTE_EVENT_DEV_PRIORITY_HIGHEST and RTE_EVENT_DEV_PRIORITY_LOWEST to map them internally to this range of priorities. [For devices supporting a power-of-2 number of priority levels, this normalization will be done via a right-shift operation, so only the top log2(max_levels) bits will be used by the event device.]

See also: rte_event.priority

Definition at line 630 of file rte_eventdev.h.

🦋 uint8_t max_event_ports

Maximum number of event ports supported by this device.

This count excludes any ports covered by max_single_link_event_port_queue_pairs.

Definition at line 644 of file rte_eventdev.h.

🦋 uint8_t max_event_port_dequeue_depth

Maximum number of events that can be dequeued at a time from an event port on this device.

A device that does not support burst dequeue (RTE_EVENT_DEV_CAP_BURST_MODE) will set this to 1.

Definition at line 649 of file rte_eventdev.h.

🦋 uint32_t max_event_port_enqueue_depth

Maximum number of events that can be enqueued at a time to an event port on this device.

A device that does not support burst enqueue (RTE_EVENT_DEV_CAP_BURST_MODE) will set this to 1.

Definition at line 656 of file rte_eventdev.h.

Maximum number of queues that can be linked to a single event port on this device.

Definition at line 663 of file rte_eventdev.h.

🦋 int32_t max_num_events

A closed system event dev has a limit on the number of events it can manage at a time. Once the number of events tracked by an eventdev exceeds this number, any enqueues of NEW events will fail. An open system event dev does not have a limit and will specify this as -1.

Definition at line 666 of file rte_eventdev.h.

🦋 uint32_t event_dev_cap

Event device capabilities flags (RTE_EVENT_DEV_CAP_*).

Definition at line 673 of file rte_eventdev.h.

Maximum number of event ports and queues, supported by this device, that are optimized for (and only capable of) single-link configurations. These ports and queues are not accounted for in max_event_ports or max_event_queues.

Definition at line 675 of file rte_eventdev.h.

🦋 uint8_t max_profiles_per_port

Maximum number of event queue link profiles per event port. A device that doesn't support multiple profiles will set this as 1.

Definition at line 681 of file rte_eventdev.h.

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. (Not a human, not a girlie — a whole robot did this 💀)

okay that's the whole page, you ate that honestly 🫶 go forth and query your event devices with confidence, bestie. this lil beauty is from DPDK, Version 26.03.0, dated rte_event_dev_info(3) — mwah, slay, periodt 💜✨

📦 where this page comes from