rte_security_capability(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’… NAME

rte_security_capability β€” bestie, this is the security capability struct, and it's kinda the whole personality of a device's security offloads ✨ (manual: Library Functions Manual, third section, iykyk πŸŽ€)


🌸 SYNOPSIS

#include <rte_security.h>

πŸ“¦ Data Fields

  • action β€” enum rte_security_session_action_type
  • protocol β€” enum rte_security_session_protocol
  • crypto_capabilities β€” const struct rte_cryptodev_capabilities *
  • ol_flags β€” uint32_t

πŸ¦‹ Detailed Description

Okay so this is the security capability definition β€” the vibe check that says what a device can actually do πŸ’–

Definition at line 1247 of file rte_security.h.

πŸ‘‘ Field Documentation

πŸ’œ action

enum rte_security_session_action_type β€” the security action type, aka what kind of move this is πŸ”₯

Definition at line 1248 of file rte_security.h.

πŸ’œ protocol

enum rte_security_session_protocol β€” the security protocol in question 🫢

Definition at line 1250 of file rte_security.h.

πŸ’œ proto

enum rte_security_ipsec_sa_protocol β€” IPsec SA protocol, slay 🌈

Definition at line 1254 of file rte_security.h.

πŸ’œ mode

enum rte_security_ipsec_sa_mode β€” IPsec SA mode ⭐

Definition at line 1256 of file rte_security.h.

πŸ’œ direction

enum rte_security_ipsec_sa_direction β€” IPsec SA direction, which way the traffic's going πŸ‘€

Definition at line 1258 of file rte_security.h.

πŸ’œ options

struct rte_security_ipsec_sa_options β€” the IPsec SA supported options πŸ’…

Definition at line 1260 of file rte_security.h.

πŸ’œ replay_win_sz_max

uint32_t β€” IPsec Anti Replay Window Size. A '0' value indicates that Anti Replay is not supported 🚫

Definition at line 1262 of file rte_security.h.

πŸ’œ ipsec

struct { ... } β€” the IPsec capability bundle πŸŽ€

πŸ’œ mtu

uint16_t β€” MTU supported for inline TX πŸ“¨

Definition at line 1270 of file rte_security.h.

πŸ’œ alg

enum rte_security_macsec_alg β€” which MACsec algorithm to be used 🧚

Definition at line 1272 of file rte_security.h.

πŸ’œ max_nb_sc

uint16_t β€” maximum number of secure channels supported πŸ”

Definition at line 1274 of file rte_security.h.

πŸ’œ max_nb_sa

uint16_t β€” maximum number of SAs supported πŸ’–

Definition at line 1276 of file rte_security.h.

πŸ’œ max_nb_sess

uint16_t β€” maximum number of SAs supported (yes, same description as the one above, no cap, I'm just the messenger 😭)

Definition at line 1278 of file rte_security.h.

πŸ’œ replay_win_sz

uint32_t β€” MACsec anti replay window size πŸͺŸ

Definition at line 1280 of file rte_security.h.

πŸ’œ relative_sectag_insert

uint16_t β€” support Sectag insertion at relative offset πŸ‘‘

Definition at line 1282 of file rte_security.h.

πŸ’œ fixed_sectag_insert

uint16_t β€” support Sectag insertion at fixed offset πŸ“Œ

Definition at line 1284 of file rte_security.h.

πŸ’œ icv_include_da_sa

uint16_t β€” ICV includes source and destination MAC addresses 🫢

Definition at line 1286 of file rte_security.h.

πŸ’œ ctrl_port_enable

uint16_t β€” control port traffic is supported βœ…

Definition at line 1288 of file rte_security.h.

πŸ’œ preserve_sectag

uint16_t β€” do not strip SecTAG after processing πŸ™ˆ

Definition at line 1290 of file rte_security.h.

πŸ’œ preserve_icv

uint16_t β€” do not strip ICV from the packet after processing πŸ™ˆ

Definition at line 1292 of file rte_security.h.

πŸ’œ validate_frames

uint16_t β€” support frame validation as per RTE_SECURITY_MACSEC_VALIDATE_* πŸ”

Definition at line 1294 of file rte_security.h.

πŸ’œ re_key

uint16_t β€” support re-keying on SA expiry πŸ”

Definition at line 1296 of file rte_security.h.

πŸ’œ anti_replay

uint16_t β€” support anti replay πŸ›‘οΈ

Definition at line 1298 of file rte_security.h.

πŸ’œ reserved

uint16_t β€” reserved bitfields for future capabilities, main character energy for later ✨

Definition at line 1300 of file rte_security.h.

πŸ’œ macsec

struct { ... } β€” the MACsec capability bundle πŸŽ€

πŸ’œ domain

enum rte_security_pdcp_domain β€” PDCP mode of operation: Control or data πŸŽ›οΈ

Definition at line 1304 of file rte_security.h.

πŸ’œ capa_flags

uint32_t β€” capability flags, see RTE_SECURITY_PDCP_* 🚩

Definition at line 1306 of file rte_security.h.

πŸ’œ pdcp

struct { ... } β€” the PDCP capability bundle πŸŽ€

πŸ’œ direction

enum rte_security_docsis_direction β€” DOCSIS direction 🧭

Definition at line 1311 of file rte_security.h.

πŸ’œ docsis

struct { ... } β€” the DOCSIS capability bundle πŸŽ€

πŸ’œ ver

enum rte_security_tls_version β€” TLS record version. 🌐

Definition at line 1316 of file rte_security.h.

πŸ’œ type

enum rte_security_tls_sess_type β€” TLS record session type. 🌐

Definition at line 1318 of file rte_security.h.

πŸ’œ ar_win_size

uint32_t β€” maximum anti replay window size supported for DTLS 1.2 record read operation. Value of 0 means anti replay check is not supported 🚫

Definition at line 1320 of file rte_security.h.

πŸ’œ tls_record

struct { ... } β€” the TLS record capability bundle πŸŽ€

πŸ’œ crypto_capabilities

const struct rte_cryptodev_capabilities* β€” corresponding crypto capabilities for security capability πŸ”₯

Definition at line 1328 of file rte_security.h.

πŸ’œ ol_flags

uint32_t β€” device offload flags πŸš€

Definition at line 1331 of file rte_security.h.

🌈 Author

Generated automatically by Doxygen for DPDK from the source code. (not a human, not a girlie, just Doxygen doing its thing πŸ’€)


okay that's the whole page bestie, go off πŸ‘‘

signing off with love β€” DPDK, Version 26.03.0 πŸ¦‹πŸ’– this was rte_security_capability(3), mwah πŸŽ€

πŸ“¦ where this page comes from