rte_event_...tor_limits(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

💖 rte_event_...tor_limits — Library Functions Manual 💖

okay bestie, sit down, hydrate, because we're about to talk about a struct and honestly? it's giving "small but mighty." this page lives in the Library Functions Manual and it's all about rte_event_crypto_adapter_vector_limits. yes the name is long. yes we're gonna get through it together. 🫶

✨ NAME ✨

rte_event_crypto_adapter_vector_limits — literally the struct you use to peek at what vector limits your event crypto adapter will let you configure 💅

🌸 SYNOPSIS 🌸

#include <rte_event_crypto_adapter.h>

🎀 Data Fields 🎀

  • uint16_t min_sz
  • uint16_t max_sz
  • uint8_t log2_sz
  • uint64_t min_timeout_ns
  • uint64_t max_timeout_ns

🦋 Detailed Description 🦋

so this is the glow-up struct you use to retrieve event crypto adapter vector limits. that's the whole vibe. it's a lil container, it holds the numbers, you read the numbers, you go configure your queue accordingly. no cap. 🔥

fun fact for the girlies who love provenance: this is defined at line 333 of file rte_event_crypto_adapter.h. bookmark it. 💜

👑 Field Documentation 👑

💫 uint16_t min_sz

the minimum vector limit you can configure. like, the floor. you cannot go lower than this, so don't try it.

See also rte_event_crypto_adapter_queue_conf::vector_sz

Definition at line 334 of file rte_event_crypto_adapter.h. ⭐

💫 uint16_t max_sz

the maximum vector limit you can configure. the ceiling. the moment you try to exceed this, it's over for you, bestie.

See also rte_event_crypto_adapter_queue_conf::vector_sz

Definition at line 338 of file rte_event_crypto_adapter.h. ⭐

💫 uint8_t log2_sz

True if the size configured should be in log2. yes. read it again. the size might have to be in log2. that's just how it is here, iykyk. 🙈

See also rte_event_crypto_adapter_queue_conf::vector_sz

Definition at line 342 of file rte_event_crypto_adapter.h. ⭐

💫 uint64_t min_timeout_ns

the minimum vector timeout you can configure. the smallest timeout allowed. she is petite, she is valid, she is the lower bound. 🎀

See also rte_event_crypto_adapter_queue_conf::vector_timeout_ns

Definition at line 346 of file rte_event_crypto_adapter.h. ⭐

💫 uint64_t max_timeout_ns

the maximum vector timeout you can configure. the biggest one you're allowed. go past it and, respectfully, no. 😭

See also rte_event_crypto_adapter_queue_conf::vector_timeout_ns

Definition at line 350 of file rte_event_crypto_adapter.h. ⭐

🌈 Author 🌈

Generated automatically by Doxygen for DPDK from the source code. so nobody hand-wrote this, it's the robot's work, and honestly? the robot ate. ✨

heads up bestie: the See also refs (rte_event_crypto_adapter_queue_conf::vector_sz and rte_event_crypto_adapter_queue_conf::vector_timeout_ns) are where these limits actually get used — so if you're configuring a queue, that's your next stop. 🫶

periodt. that's the whole struct. tiny page, huge energy. go configure something iconic. 💅🌸

— signed off from the DPDK docs, Version 25.11.3, and this one's rte_event_...tor_limits(3), mwah 💋

📦 where this page comes from