rte_securi...d_lifetime(3)

✨ rte_security_tls_record_lifetime ✨

okay bestie, gather round, because this one is literally the vibe check for your TLS record session's whole lifespan 💀 no cap.

---

🌸 NAME 🌸

rte_security_tls_record_lifetime — the little struct that decides how long your TLS record session gets to live before it's done 🎀

---

✨ SYNOPSIS ✨

#include <rte_security.h>

💅 Data Fields

• uint64_t packets_soft_limit
• uint64_t packets_hard_limit

---

🦋 Detailed Description 🦋

bestie this struct is how you configure the soft and hard lifetime of a TLS record session, fr fr 🫶

so the lifetime of a TLS record session specifies the maximum number of packets that can be processed. and listen — once the hard limit gets reached, TLS record processing operations start failing. like, that's it, that's the end, no more packets for you 😭

but wait, there's more 💖 Soft limits can be specified to generate a notification when the TLS record session is approaching hard limits for lifetime. what does that look like? it would result in a warning returned in rte_crypto_op.aux_flags. so you get a lil heads-up before everything goes down 🚨

Definition at line 666 of file rte_security.h.

---

🌈 Field Documentation 🌈

💜 uint64_t packets_soft_limit

Soft expiry limit in number of packets 🍓

Definition at line 668 of file rte_security.h.

💜 uint64_t packets_hard_limit

Hard expiry limit in number of packets 🔥

Definition at line 670 of file rte_security.h.

---

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. yes bestie, the robots wrote this one, we're just here to make it cute 🧚

---

okay that's the whole page, you ate that 💅 and for the sign-off: this lil masterpiece lives in DPDK, Version 25.11.3, and it's serving rte_security_tls_record_lifetime(3) realness, mwah 💋 periodt ✨