From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org, konstantin.ananyev@intel.com, akhil.goyal@nxp.com
Cc: Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-dev] [PATCH 0/2]
Date: Thu, 29 Aug 2019 09:45:15 +0100 [thread overview]
Message-ID: <1567068317-1582-1-git-send-email-bernard.iremonger@intel.com> (raw)
This patch set, sets the default code path in the ipsec-secgw
application to use the librte_ipsec.
The _old test scripts have been modified to use the legacy code
patch
Bernard Iremonger (2):
examples/ipsec-secgw: set default to IPsec library mode
examples/ipsec-secgw: add -l 0 parameter to old scripts
doc/guides/rel_notes/release_19_11.rst | 8 ++++
doc/guides/sample_app_ug/ipsec_secgw.rst | 6 ++-
examples/ipsec-secgw/ipsec-secgw.c | 44 ++++++++++++++--------
.../ipsec-secgw/test/trs_3descbc_sha1_old_defs.sh | 2 +-
.../ipsec-secgw/test/trs_aescbc_sha1_old_defs.sh | 2 +-
.../ipsec-secgw/test/trs_aesctr_sha1_old_defs.sh | 2 +-
.../test/trs_aesgcm_inline_crypto_old_defs.sh | 2 +-
examples/ipsec-secgw/test/trs_aesgcm_old_defs.sh | 2 +-
.../ipsec-secgw/test/tun_3descbc_sha1_old_defs.sh | 2 +-
.../ipsec-secgw/test/tun_aescbc_sha1_old_defs.sh | 2 +-
.../ipsec-secgw/test/tun_aesctr_sha1_old_defs.sh | 2 +-
.../test/tun_aesgcm_inline_crypto_old_defs.sh | 2 +-
examples/ipsec-secgw/test/tun_aesgcm_old_defs.sh | 2 +-
13 files changed, 50 insertions(+), 28 deletions(-)
--
2.7.4
next reply other threads:[~2019-08-29 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 8:45 Bernard Iremonger [this message]
2019-08-29 8:45 ` [dpdk-dev] [PATCH 1/2] examples/ipsec-secgw: set default to IPsec library mode Bernard Iremonger
2019-08-29 8:45 ` [dpdk-dev] [PATCH 2/2] examples/ipsec-secgw: add -l 0 parameter to old scripts Bernard Iremonger
-- strict thread matches above, loose matches on Subject: below --
2019-08-29 8:39 [dpdk-dev] [PATCH 0/2] Bernard Iremonger
2014-05-16 10:15 Vadim Suraev
2014-05-15 21:20 Vadim Suraev
2014-05-15 21:33 ` Thomas Monjalon
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=1567068317-1582-1-git-send-email-bernard.iremonger@intel.com \
--to=bernard.iremonger@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).