VECTOR_TIMEOUT_NS(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💅 rte_event_crypto_adapter_queue_conf ✨

okay bestie, so this page is literally the manpage for rte_event_crypto_adapter_queue_conf — that's the function-name vibe from the Library Functions Manual, and it's genuinely iconic. It's a struct, it lives in DPDK, and it's the queue config glow-up for the crypto adapter. Let's get into it 🎀

🌸 SYNOPSIS 🌸

#include <rte_event_crypto_adapter.h>

✨ Data Fields ✨

  • uint32_t flags
  • struct rte_event ev
  • uint16_t vector_sz
  • uint64_t vector_timeout_ns
  • struct rte_mempool * vector_mp

🦋 Detailed Description 🦋

It's giving Adapter queue configuration structure. Periodt.

Fr fr, its definition lives at line 293 of the file rte_event_crypto_adapter.h.

💖 Field Documentation 💖

🎀 uint32_t flags

The flags for handling crypto operations, no cap.

See also: RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR

Defined at line 294 of the file rte_event_crypto_adapter.h.

🦋 struct rte_event ev

So here's the tea ☕ — if the HW supports cryptodev queue pair to event queue binding, the application is expected to fill in the event information. That's your job, bestie, not the library's.

See also: RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_QP_EV_BIND

Defined at line 298 of the file rte_event_crypto_adapter.h.

🧚 uint16_t vector_sz

This one tells you the maximum number of crypto operations that get combined to form a vector. Like, how many little guys get to squad up together 💫

See also:

  • rte_event_crypto_adapter_vector_limits::min_sz
  • rte_event_crypto_adapter_vector_limits::max_sz
Valid when the RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR flag is set in rte_event_crypto_adapter_queue_conf::flags.

Defined at line 303 of the file rte_event_crypto_adapter.h.

🌈 uint64_t vector_timeout_ns

The maximum number of nanoseconds to wait while aggregating crypto operations — lowkey the patience setting for your vector. It should be within the vectorization limits of the adapter, so don't just make up a number 🙈

See also:

  • rte_event_crypto_adapter_vector_limits::min_timeout_ns
  • rte_event_crypto_adapter_vector_limits::max_timeout_ns
Valid when the RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR flag is set in rte_event_crypto_adapter_queue_conf::flags.

Defined at line 311 of the file rte_event_crypto_adapter.h.

🍓 struct rte_mempool* vector_mp

This is the mempool that should be used for allocating the rte_event_vector container. And listen — it should be created by using rte_event_vector_pool_create, okay? That's the whole assignment.

Valid when the RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR flag is set in rte_event_crypto_adapter_queue_conf::flags.

See also: rte_event_crypto_adapter_queue_conf::flags

Defined at line 321 of the file rte_event_crypto_adapter.h.

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. So iconic of it, honestly — the docs literally generated themselves. Main character energy ✨

and that's the whole page bestie!! 🫶 this was DPDK, Version 26.03.0, titled rte_event_..._queue_conf(3) — go forth and configure those queues, you ate 💅🔥

📦 where this page comes from