From: Radu Nicolau <radu.nicolau@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com, anoobj@marvell.com,
konstantin.ananyev@intel.com,
Radu Nicolau <radu.nicolau@intel.com>
Subject: [dpdk-dev] [PATCH v5 0/2] ipsec: add transmit segmentation offload support
Date: Thu, 28 Oct 2021 13:22:44 +0100 [thread overview]
Message-ID: <20211028122246.2689255-1-radu.nicolau@intel.com> (raw)
Add transmit segmentation offload support to the IPsec library and IPsec
Security GW sample app.
These patches were split from previously sent patchsets with feedback addressed
https://patchwork.dpdk.org/project/dpdk/patch/20211013121331.300245-7-radu.nicolau@intel.com/
https://patchwork.dpdk.org/project/dpdk/patch/20211001095202.3343782-5-radu.nicolau@intel.com/
Radu Nicolau (2):
ipsec: add TSO support
examples/ipsec-secgw: add support for TCP TSO
doc/guides/prog_guide/ipsec_lib.rst | 2 +
doc/guides/rel_notes/release_21_11.rst | 5 +
doc/guides/sample_app_ug/ipsec_secgw.rst | 11 ++
examples/ipsec-secgw/ipsec-secgw.c | 4 +
examples/ipsec-secgw/ipsec.h | 1 +
examples/ipsec-secgw/ipsec_process.c | 23 ++++
examples/ipsec-secgw/sa.c | 25 +++-
lib/ipsec/esp_outb.c | 141 ++++++++++++++++++-----
8 files changed, 177 insertions(+), 35 deletions(-)
--
v2: addressed feedback and rebased to RC1
v3: added check for offload caps and removed duplicate code
v4: updated check for offload caps and reworked the sample app patch for TCP only
v5: reworked ptype check
2.25.1
next reply other threads:[~2021-10-28 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 12:22 Radu Nicolau [this message]
2021-10-28 12:22 ` [dpdk-dev] [PATCH v5 1/2] ipsec: add TSO support Radu Nicolau
2021-10-31 20:57 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-31 21:02 ` Akhil Goyal
2021-10-28 12:22 ` [dpdk-dev] [PATCH v5 2/2] examples/ipsec-secgw: add support for TCP TSO Radu Nicolau
2021-10-31 20:56 ` [dpdk-dev] [EXT] " 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=20211028122246.2689255-1-radu.nicolau@intel.com \
--to=radu.nicolau@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--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).