Searched refs:SA (Results 1 – 12 of 12) sorted by relevance
15 SA level API18 This API operates on the IPsec Security Association (SA) level.19 It provides functionality that allows user for given SA to process73 - update SA replay window105 - update SA replay window154 SA database API157 SA database(SAD) is a table with <key, value> pairs.301 printf("SA not found for key index %d\n", i);303 printf("SA pointer is %p\n", vals[i]);327 statistics. Per SA telemetry statistics can be enabled using[all …]
196 Security Association (SA) as part of a crypto session creation including234 | | SADB lookup | | <------ SA maps to cryptodev session243 +--------V--------+ | | create <-- SA is added to hw685 example if the security session specifies an egress IPsec SA, then multiple686 flows can be specified to that SA. In the case of an ingress IPsec SA then695 | IPsec SA | <------ Build security flow action of705 | NIC PMD | <------ Add/Remove SA to/from hw context715 * Add/Delete SA flow:716 To add a new inline SA construct a rte_flow_item for Ethernet + IP + ESP717 using the SA selectors and the ``rte_crypto_ipsec_xform`` as the ``rte_flow_action``.
2225 ``rte_security_session``. The SA is identified according to the IP and ESP
22 Associations (SA) are stored in a table and the routing is implemented32 These modes can be selected during the SA creation configuration.48 * Perform Inbound SA lookup for ESP packets based on their SPI.59 * Perform Outbound SA lookup for packets that need IPsec protection.120 * Each SA must be handle by a unique lcore (*1 RX queue per port*).374 your SP, SA, Routing, Flow and Neighbour tables.521 SA rule syntax526 The SA rule syntax is shown as follows:682 the SA to be performed with look aside protocol offload to HW766 * Option to enable per SA telemetry.[all …]
228 for inbound SA with min SPI of 6.242 - ``Max SA's for outbound inline IPsec`` (default ``4096``)244 Max number of SA's supported for outbound inline IPsec processing can be254 - ``Enable custom SA action`` (default ``0``)256 Custom SA action can be enabled by specifying ``custom_sa_act`` ``devargs`` parameter.262 With the above configuration, application can enable custom SA action. This264 rather than only match a single SA.466 for inbound SA with min SPI of 6 for traffic aggregated on inline device.478 for inbound SA with max SPI of 128 for traffic aggregated on inline device.
627 u32 SA:7; /* must be between 64-127 */ member633 u32 SA:7; /* must be between 64-127 */
111 [IPsec SA] (@ref rte_ipsec_sa.h),
68 #SA rules
65 #SA rules
340 * Added support for SA telemetry.590 ``rte_security_ipsec_xform`` to allow applications to configure SA soft600 applications to start from an arbitrary ESN value for debug and SA lifetime
240 * Added Security Associations (SA) Database API to ``librte_ipsec``. A new
988 Configure MACsec secure association (SA)::