From: Mariusz Drost <mariuszx.drost@intel.com>
To: radu.nicolau@intel.com, akhil.goyal@nxp.com,
konstantin.ananyev@intel.com
Cc: dev@dpdk.org, Mariusz Drost <mariuszx.drost@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/2] fix SAD selection logic
Date: Tue, 24 Sep 2019 12:35:37 +0200 [thread overview]
Message-ID: <20190924103539.12052-1-mariuszx.drost@intel.com> (raw)
In-Reply-To: <20190905123523.172-1-mariuszx.drost@intel.com>
Code fix for SAD selection logic by splitting SAD into IPv4 SAD and
IPv6 SAD. Test scripts updated to reflect changes.
v2:
* Added linux_test.sh
* Modified ep0.cfg and ep1.cfg files to run with ipsec-secgw app
Mariusz Drost (2):
examples/ipsec-secgw: fix SAD selection logic
examples/ipsec-secgw: tests for split SAD
examples/ipsec-secgw/ep0.cfg | 58 ++-
examples/ipsec-secgw/ep1.cfg | 62 ++-
examples/ipsec-secgw/ipsec-secgw.c | 48 ++-
examples/ipsec-secgw/ipsec.c | 5 +-
examples/ipsec-secgw/ipsec.h | 21 +-
examples/ipsec-secgw/sa.c | 396 ++++++++++++------
examples/ipsec-secgw/test/common_defs.sh | 7 +-
.../test/{linux_test6.sh => linux_test.sh} | 94 ++++-
examples/ipsec-secgw/test/linux_test4.sh | 78 ----
examples/ipsec-secgw/test/run_test.sh | 42 +-
.../ipsec-secgw/test/trs_3descbc_sha1_defs.sh | 7 +-
.../test/trs_3descbc_sha1_esn_defs.sh | 7 +-
.../ipsec-secgw/test/trs_aescbc_sha1_defs.sh | 7 +-
.../test/trs_aescbc_sha1_esn_defs.sh | 7 +-
.../ipsec-secgw/test/trs_aesctr_sha1_defs.sh | 7 +-
.../test/trs_aesctr_sha1_esn_defs.sh | 7 +-
examples/ipsec-secgw/test/trs_aesgcm_defs.sh | 7 +-
.../ipsec-secgw/test/trs_aesgcm_esn_defs.sh | 7 +-
.../test/tun_3descbc_sha1_common_defs.sh | 68 +++
.../ipsec-secgw/test/tun_3descbc_sha1_defs.sh | 77 +++-
.../test/tun_3descbc_sha1_esn_defs.sh | 77 +++-
.../test/tun_aescbc_sha1_common_defs.sh | 64 +++
.../ipsec-secgw/test/tun_aescbc_sha1_defs.sh | 77 +++-
.../test/tun_aescbc_sha1_esn_defs.sh | 77 +++-
.../test/tun_aesctr_sha1_common_defs.sh | 64 +++
.../ipsec-secgw/test/tun_aesctr_sha1_defs.sh | 77 +++-
.../test/tun_aesctr_sha1_esn_defs.sh | 77 +++-
.../test/tun_aesgcm_common_defs.sh | 56 +++
examples/ipsec-secgw/test/tun_aesgcm_defs.sh | 77 +++-
.../ipsec-secgw/test/tun_aesgcm_esn_defs.sh | 77 +++-
30 files changed, 1397 insertions(+), 338 deletions(-)
rename examples/ipsec-secgw/test/{linux_test6.sh => linux_test.sh} (50%)
delete mode 100644 examples/ipsec-secgw/test/linux_test4.sh
--
2.17.1
next prev parent reply other threads:[~2019-09-24 10:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 12:35 [dpdk-dev] [PATCH 0/2] fix SAD selection logic Mariusz Drost
2019-09-05 12:35 ` [dpdk-dev] [PATCH 1/2] examples/ipsec-secgw: " Mariusz Drost
2019-09-05 12:35 ` [dpdk-dev] [PATCH 2/2] examples/ipsec-secgw: tests for split SAD Mariusz Drost
2019-09-24 10:35 ` Mariusz Drost [this message]
2019-09-24 10:35 ` [dpdk-dev] [PATCH v2 1/2] examples/ipsec-secgw: fix SAD selection logic Mariusz Drost
2019-09-24 12:18 ` Ananyev, Konstantin
2019-10-02 15:43 ` Nicolau, Radu
2019-10-10 13:43 ` Akhil Goyal
2019-10-11 13:24 ` Ananyev, Konstantin
2019-10-11 14:02 ` Akhil Goyal
2019-10-11 16:38 ` Ananyev, Konstantin
2019-10-15 13:53 ` Akhil Goyal
2019-10-16 10:20 ` Ananyev, Konstantin
2019-09-24 10:35 ` [dpdk-dev] [PATCH v2 2/2] examples/ipsec-secgw: tests for split SAD Mariusz Drost
2019-09-24 12:47 ` Ananyev, Konstantin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190924103539.12052-1-mariuszx.drost@intel.com \
--to=mariuszx.drost@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=radu.nicolau@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).