401633d9c1
According to RFC 4301 IPSec implementation needs an inbound SA database (SAD). For each incoming inbound IPSec-protected packet (ESP or AH) it has to perform a lookup within it's SAD. Lookup should be performed by: Security Parameters Index (SPI) + destination IP (DIP) + source IP (SIP) or SPI + DIP or SPI only and an implementation has to return the 'longest' existing match. This patch extend DPDK IPsec library with inbound security association database (SAD) API implementation that: - conforms to the RFC requirements above - can scale up to millions of entries - supports fast lookups - supports incremental updates Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
22 lines
400 B
Plaintext
22 lines
400 B
Plaintext
EXPERIMENTAL {
|
|
global:
|
|
|
|
rte_ipsec_pkt_crypto_group;
|
|
rte_ipsec_pkt_crypto_prepare;
|
|
rte_ipsec_pkt_process;
|
|
rte_ipsec_sa_fini;
|
|
rte_ipsec_sa_init;
|
|
rte_ipsec_sa_size;
|
|
rte_ipsec_sa_type;
|
|
rte_ipsec_sad_add;
|
|
rte_ipsec_sad_create;
|
|
rte_ipsec_sad_del;
|
|
rte_ipsec_sad_destroy;
|
|
rte_ipsec_sad_find_existing;
|
|
rte_ipsec_sad_lookup;
|
|
rte_ipsec_ses_from_crypto;
|
|
rte_ipsec_session_prepare;
|
|
|
|
local: *;
|
|
};
|