diff options
| author |   Yulong Pei <yulong.pei@intel.com> | 2020-08-19 18:30:34 +0800 |
|---|---|---|
| committer |   Jan Gelety <jgelety@cisco.com> | 2020-09-11 12:52:45 +0000 |
| commit | d12f510caf3bb83695488684eb07de79b3e753b9 (patch) | |
| tree | 8209b17b3c4d8180868cba9b9815e5f71cf7c56d /resources/api | |
| parent | d3763454526d2886ce8d0210b788c1d90540e9aa (diff) | |
Add ipsec async mode performance test cases
In VPP 20.05, vpp added async crypto engine that support to use QAT hardware
to do encryption and decryption, vnet/ipsec enabled async mode to use async
crypto engine.
Current async crypto engine also use dpdk_cryptodev as async handlers, in the
future it may add other native QAT driver as async handlers.
Note that async crypto engine is to support vnet/ipsec, it is different
with current existing dpdk backend which itself has ESP implementation
in plugins/dpdk/ipsec.
Change-Id: I4e6eaa7ca1eddb8b1c45212de0684fb26907119b
Signed-off-by: Yulong Pei <yulong.pei@intel.com>
Diffstat (limited to 'resources/api')
| -rw-r--r-- | resources/api/vpp/supported_crcs.yaml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/resources/api/vpp/supported_crcs.yaml b/resources/api/vpp/supported_crcs.yaml index c4bc243aae..c3eb03226b 100644 --- a/resources/api/vpp/supported_crcs.yaml +++ b/resources/api/vpp/supported_crcs.yaml @@ -134,6 +134,8 @@ ipsec_spd_entry_add_del_reply: '0x9ffac24b' # dev ipsec_tunnel_if_add_del: '0x2b135e68' # perf ipsec_tunnel_if_add_del_reply: '0x5383d31f' # perf + ipsec_set_async_mode: '0xa6465f7c' #perf + ipsec_set_async_mode_reply: '0xe8d4e804' #perf # ^^ tc01-64B-1c-ethip4ipsec1tnlhw-ip4base-int-aes256gcm-mrr # ^ See select_backend. # l2_fib_table_dump / details # honeycomb |