From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/4] ipsec: add AES-CTR and 3DES-CBC support
Date: Mon, 4 Mar 2019 16:38:57 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258012413F78D@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <20190225120745.61836-1-roy.fan.zhang@intel.com>
>
> This patchset adds the AES-CTR and 3DES-CBC cipher algorithms
> support to ipsec library. The test scripts for ipsec-secgw
> sample application are added too.
>
> v3:
> - fixed a bug in 3DES.
>
> v2:
> - removed unsupported tests.
>
> Fan Zhang (4):
> ipsec: add AES-CTR algorithm support
> ipsec-secgw: add test scripts for aes ctr
> ipsec: add 3DES-CBC algorithm support
> ipsec-secgw: add 3des test files
>
> examples/ipsec-secgw/test/common_defs.sh | 4 +-
> examples/ipsec-secgw/test/run_test.sh | 14 ++-
> .../test/trs_3descbc_sha1_common_defs.sh | 73 +++++++++++
> examples/ipsec-secgw/test/trs_3descbc_sha1_defs.sh | 67 ++++++++++
> .../test/trs_3descbc_sha1_esn_atom_defs.sh | 5 +
> .../ipsec-secgw/test/trs_3descbc_sha1_esn_defs.sh | 66 ++++++++++
> .../ipsec-secgw/test/trs_3descbc_sha1_old_defs.sh | 5 +
> .../test/trs_aesctr_sha1_common_defs.sh | 69 +++++++++++
> examples/ipsec-secgw/test/trs_aesctr_sha1_defs.sh | 67 ++++++++++
> .../test/trs_aesctr_sha1_esn_atom_defs.sh | 5 +
> .../ipsec-secgw/test/trs_aesctr_sha1_esn_defs.sh | 66 ++++++++++
> .../ipsec-secgw/test/trs_aesctr_sha1_old_defs.sh | 5 +
> .../test/tun_3descbc_sha1_common_defs.sh | 72 +++++++++++
> examples/ipsec-secgw/test/tun_3descbc_sha1_defs.sh | 70 +++++++++++
> .../test/tun_3descbc_sha1_esn_atom_defs.sh | 5 +
> .../ipsec-secgw/test/tun_3descbc_sha1_esn_defs.sh | 70 +++++++++++
> .../ipsec-secgw/test/tun_3descbc_sha1_old_defs.sh | 5 +
> .../test/tun_aesctr_sha1_common_defs.sh | 68 ++++++++++
> examples/ipsec-secgw/test/tun_aesctr_sha1_defs.sh | 70 +++++++++++
> .../test/tun_aesctr_sha1_esn_atom_defs.sh | 5 +
> .../ipsec-secgw/test/tun_aesctr_sha1_esn_defs.sh | 70 +++++++++++
> .../ipsec-secgw/test/tun_aesctr_sha1_old_defs.sh | 5 +
> lib/librte_ipsec/crypto.h | 17 +++
> lib/librte_ipsec/sa.c | 137 +++++++++++++++++----
> lib/librte_ipsec/sa.h | 24 ++++
> 25 files changed, 1040 insertions(+), 24 deletions(-)
> create mode 100644 examples/ipsec-secgw/test/trs_3descbc_sha1_common_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_3descbc_sha1_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_3descbc_sha1_esn_atom_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_3descbc_sha1_esn_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_3descbc_sha1_old_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_aesctr_sha1_common_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_aesctr_sha1_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_aesctr_sha1_esn_atom_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_aesctr_sha1_esn_defs.sh
> create mode 100644 examples/ipsec-secgw/test/trs_aesctr_sha1_old_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_3descbc_sha1_common_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_3descbc_sha1_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_3descbc_sha1_esn_atom_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_3descbc_sha1_esn_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_3descbc_sha1_old_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_aesctr_sha1_common_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_aesctr_sha1_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_aesctr_sha1_esn_atom_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_aesctr_sha1_esn_defs.sh
> create mode 100644 examples/ipsec-secgw/test/tun_aesctr_sha1_old_defs.sh
>
> --
Reviewed-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.14.5
next prev parent reply other threads:[~2019-03-04 16:39 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 16:32 [dpdk-dev] [PATCH " Fan Zhang
2019-02-18 16:32 ` [dpdk-dev] [PATCH 1/4] ipsec: add AES-CTR algorithm support Fan Zhang
2019-02-18 16:32 ` [dpdk-dev] [PATCH 2/4] ipsec-secgw: add test scripts for aes ctr Fan Zhang
2019-02-18 16:32 ` [dpdk-dev] [PATCH 3/4] ipsec: add 3DES-CBC algorithm support Fan Zhang
2019-02-18 16:32 ` [dpdk-dev] [PATCH 4/4] ipsec-secgw: add 3des test files Fan Zhang
2019-02-19 15:32 ` [dpdk-dev] [PATCH v2 0/4] ipsec: add AES-CTR and 3DES-CBC support Fan Zhang
2019-02-19 15:32 ` [dpdk-dev] [PATCH v2 1/4] ipsec: add AES-CTR algorithm support Fan Zhang
2019-02-22 12:43 ` Ananyev, Konstantin
2019-03-19 14:32 ` Akhil Goyal
2019-03-19 14:32 ` Akhil Goyal
2019-02-19 15:32 ` [dpdk-dev] [PATCH v2 2/4] ipsec-secgw: add test scripts for aes ctr Fan Zhang
2019-02-22 12:39 ` Ananyev, Konstantin
2019-02-19 15:32 ` [dpdk-dev] [PATCH v2 3/4] ipsec: add 3DES-CBC algorithm support Fan Zhang
2019-02-22 12:38 ` Ananyev, Konstantin
2019-03-19 14:46 ` Akhil Goyal
2019-03-19 14:46 ` Akhil Goyal
2019-02-19 15:32 ` [dpdk-dev] [PATCH v2 4/4] ipsec-secgw: add 3des test files Fan Zhang
2019-02-22 12:40 ` Ananyev, Konstantin
2019-02-25 12:07 ` [dpdk-dev] [PATCH v3 0/4] ipsec: add AES-CTR and 3DES-CBC support Fan Zhang
2019-02-25 12:07 ` [dpdk-dev] [PATCH v3 1/4] ipsec: add AES-CTR algorithm support Fan Zhang
2019-02-25 12:07 ` [dpdk-dev] [PATCH v3 2/4] ipsec-secgw: add test scripts for aes ctr Fan Zhang
2019-02-25 12:07 ` [dpdk-dev] [PATCH v3 3/4] ipsec: add 3DES-CBC algorithm support Fan Zhang
2019-02-25 12:07 ` [dpdk-dev] [PATCH v3 4/4] ipsec-secgw: add 3des test files Fan Zhang
2019-03-04 16:38 ` Ananyev, Konstantin [this message]
2019-03-20 13:51 ` [dpdk-dev] [PATCH v4 0/4] ipsec: support AES-CTR and 3DES-CBC Fan Zhang
2019-03-20 13:51 ` Fan Zhang
2019-03-20 13:51 ` [dpdk-dev] [PATCH v4 1/4] ipsec: support AES-CTR Fan Zhang
2019-03-20 13:51 ` Fan Zhang
2019-03-20 13:51 ` [dpdk-dev] [PATCH v4 2/4] ipsec-secgw: add test scripts for aes ctr Fan Zhang
2019-03-20 13:51 ` Fan Zhang
2019-03-20 13:51 ` [dpdk-dev] [PATCH v4 3/4] ipsec: support 3DES-CBC Fan Zhang
2019-03-20 13:51 ` Fan Zhang
2019-03-20 13:51 ` [dpdk-dev] [PATCH v4 4/4] ipsec-secgw: add 3des test files Fan Zhang
2019-03-20 13:51 ` Fan Zhang
2019-03-20 15:38 ` [dpdk-dev] [PATCH v5 0/5] ipsec: support AES-CTR and 3DES-CBC Fan Zhang
2019-03-20 15:38 ` Fan Zhang
2019-03-20 15:38 ` [dpdk-dev] [PATCH v5 1/5] ipsec: support AES-CTR Fan Zhang
2019-03-20 15:38 ` Fan Zhang
2019-03-22 11:53 ` Akhil Goyal
2019-03-22 11:53 ` Akhil Goyal
2019-03-22 12:46 ` Ananyev, Konstantin
2019-03-22 12:46 ` Ananyev, Konstantin
2019-03-22 13:01 ` Akhil Goyal
2019-03-22 13:01 ` Akhil Goyal
2019-03-20 15:38 ` [dpdk-dev] [PATCH v5 2/5] ipsec-secgw: add test scripts for aes ctr Fan Zhang
2019-03-20 15:38 ` Fan Zhang
2019-03-20 15:38 ` [dpdk-dev] [PATCH v5 3/5] ipsec: support 3DES-CBC Fan Zhang
2019-03-20 15:38 ` Fan Zhang
2019-03-20 15:38 ` [dpdk-dev] [PATCH v5 4/5] ipsec-secgw: add 3des test files Fan Zhang
2019-03-20 15:38 ` Fan Zhang
2019-03-20 15:38 ` [dpdk-dev] [PATCH v5 5/5] doc: update release note Fan Zhang
2019-03-20 15:38 ` Fan Zhang
2019-03-22 14:59 ` [dpdk-dev] [PATCH v5 0/5] ipsec: support AES-CTR and 3DES-CBC Akhil Goyal
2019-03-22 14:59 ` Akhil Goyal
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=2601191342CEEE43887BDE71AB977258012413F78D@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).