From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
Cc: akhil.goyal@nxp.com, Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [PATCH v3 0/4] examples/ipsec-secgw: support packet
Date: Wed, 26 Jun 2019 00:16:45 +0100 [thread overview]
Message-ID: <20190625231649.22560-1-konstantin.ananyev@intel.com> (raw)
In-Reply-To: <20190606115151.27805-1-konstantin.ananyev@intel.com>
v1 -> v2
- merge with latest mainline
- update sample app guide
v2 -> v3
address Akhil comments:
- merge with latest mainline
- squash sample app guide changes with ipsec-secgw changes
Add into ipsec-secgw ability to fragment packet bigger then mtu,
and reassemble fragmented packet.
To support these features ipsec-secgw relies on librte_ipsec ability
to handle multi-segment packets.
Also when reassemble/fragmentation support is enabled, attached
crypto devices have to support 'In Place SGL' offload capability.
To be able to work properly these changes require the following patches:
[1] lib/librte_ip_frag: Remove PKT_TX_IP_CKSUM offload flags
http://patches.dpdk.org/patch/53475/mbox/
[2] ip_frag: fix IPv6 fragment size calculation
http://patches.dpdk.org/patch/54489/mbox/
to be applied first.
Konstantin Ananyev (4):
examples/ipsec-secgw: fix invalid packet length
examples/ipsec-secgw: support packet fragmentation and reassembly
examples/ipsec-secgw: add multi-segment test cases
examples/ipsec-secgw: add bypass test case
doc/guides/sample_app_ug/ipsec_secgw.rst | 22 +-
examples/ipsec-secgw/ipsec-secgw.c | 402 ++++++++++++++++++++---
examples/ipsec-secgw/ipsec.h | 1 +
examples/ipsec-secgw/meson.build | 2 +-
examples/ipsec-secgw/test/bypass_defs.sh | 45 +++
examples/ipsec-secgw/test/common_defs.sh | 18 +-
examples/ipsec-secgw/test/data_rxtx.sh | 18 +-
examples/ipsec-secgw/test/linux_test4.sh | 17 +-
examples/ipsec-secgw/test/linux_test6.sh | 17 +-
examples/ipsec-secgw/test/run_test.sh | 5 +-
10 files changed, 484 insertions(+), 63 deletions(-)
create mode 100644 examples/ipsec-secgw/test/bypass_defs.sh
--
2.17.1
next prev parent reply other threads:[~2019-06-25 23:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 18:44 [dpdk-dev] [PATCH 0/3] examples/ipsec-secgw: support packet fragmentation Konstantin Ananyev
2019-05-27 18:44 ` [dpdk-dev] [PATCH 1/3] examples/ipsec-secgw: fix invalid packet length Konstantin Ananyev
2019-05-27 18:44 ` [dpdk-dev] [PATCH 2/3] examples/ipsec-secgw: support packet fragmentation and reassembly Konstantin Ananyev
2019-05-27 18:44 ` [dpdk-dev] [PATCH 3/3] examples/ipsec-secgw: add multi-segment test cases Konstantin Ananyev
2019-06-06 11:51 ` [dpdk-dev] [PATCH v2 0/5] examples/ipsec-secgw: support packet Konstantin Ananyev
2019-06-06 11:51 ` [dpdk-dev] [PATCH v2 1/5] examples/ipsec-secgw: fix invalid packet length Konstantin Ananyev
2019-06-25 13:04 ` Akhil Goyal
2019-06-25 13:07 ` Ananyev, Konstantin
2019-06-06 11:51 ` [dpdk-dev] [PATCH v2 2/5] examples/ipsec-secgw: support packet fragmentation and reassembly Konstantin Ananyev
2019-06-06 11:51 ` [dpdk-dev] [PATCH v2 3/5] examples/ipsec-secgw: add multi-segment test cases Konstantin Ananyev
2019-06-06 11:51 ` [dpdk-dev] [PATCH v2 4/5] examples/ipsec-secgw: add bypass test case Konstantin Ananyev
2019-06-06 11:51 ` [dpdk-dev] [PATCH v2 5/5] doc: update ipsec-secgw guide Konstantin Ananyev
2019-06-25 23:16 ` Konstantin Ananyev [this message]
2019-06-25 23:16 ` [dpdk-dev] [PATCH v3 1/4] examples/ipsec-secgw: fix invalid packet length Konstantin Ananyev
2019-06-25 23:16 ` [dpdk-dev] [PATCH v3 2/4] examples/ipsec-secgw: support packet fragmentation and reassembly Konstantin Ananyev
2019-06-25 23:16 ` [dpdk-dev] [PATCH v3 3/4] examples/ipsec-secgw: add multi-segment test cases Konstantin Ananyev
2019-06-25 23:16 ` [dpdk-dev] [PATCH v3 4/4] examples/ipsec-secgw: add bypass test case Konstantin Ananyev
2019-07-01 11:43 ` [dpdk-dev] [PATCH v3 0/4] examples/ipsec-secgw: support packet 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=20190625231649.22560-1-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
/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).