RTE_ETH_EVENT_IPSEC_DESC(3)

✨ rte_eth_event_ipsec_desc(3) ✨

okay bestie, so this is a page from the Library Functions Manual and it's literally just one struct's whole story 💅 her name is rte_eth_event_ipsec_desc and she's the glow-up descriptor for the RTE_ETH_EVENT_IPSEC event. no cap.

---

🌸 SYNOPSIS 🌸

#include <rte_ethdev.h>

🎀 Data Fields 🎀

• enum rte_eth_event_ipsec_subtype subtype
• uint64_t metadata

---

💖 Detailed Description 💖

so basically, this is the descriptor for the RTE_ETH_EVENT_IPSEC event 🦋. the eth dev uses it to send along extra info about the IPsec offload event — like, the event itself walks in and this struct is her little entourage carrying the details ✨.

fr fr, it's defined at line 4175 of the file rte_ethdev.h. iconic placement.

---

👑 Field Documentation 👑

💜 enum rte_eth_event_ipsec_subtype subtype

this one is the type of the RTE_ETH_EVENT_IPSEC_* event 💫 — she says WHICH ipsec event we're dealing with.

defined at line 4177 of file rte_ethdev.h. noted. 📝

🍓 uint64_t metadata

the event specific metadata 🫶 — the little bonus payload that comes attached.

and here's the tea ☕: for the following events, the userdata registered with the rte_security_session gets returned as the metadata:

• RTE_ETH_EVENT_IPSEC_ESN_OVERFLOW
• RTE_ETH_EVENT_IPSEC_SA_TIME_EXPIRY
• RTE_ETH_EVENT_IPSEC_SA_BYTE_EXPIRY
• RTE_ETH_EVENT_IPSEC_SA_PKT_EXPIRY
• RTE_ETH_EVENT_IPSEC_SA_BYTE_HARD_EXPIRY
• RTE_ETH_EVENT_IPSEC_SA_PKT_HARD_EXPIRY

like, all six of those just hand your userdata back to you as the metadata. slay 🌈.

⭐ See also ⭐

• struct rte_security_session_conf

and yeah, this field is defined at line 4195 of file rte_ethdev.h 💀 (she's down there, deep in the header, living her best life).

---

🌟 Author 🌟

generated automatically by Doxygen for DPDK, straight from the source code — so basically the robot wrote it, not a person 🙈.

---

and that's a wrap, bestie 💖 this page came to you from DPDK, Version 25.11.3 🦋 mwah, go forth and handle your IPsec events, you main character 👑✨