From: Xin Long <lucien.xin@gmail.com>
To: netdev@vger.kernel.org
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Florian Westphal <fw@strlen.de>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: [PATCH ipsec-next 0/3] xfrm: add offload support for esp beet mode
Date: Thu, 26 Mar 2020 17:02:28 +0800 [thread overview]
Message-ID: <cover.1585213292.git.lucien.xin@gmail.com> (raw)
This patchset is to add gso_segment functions for esp4 and esp6
beet mode, and prep function for both, and tested with 6 cases:
1. IPv4 INNER ADDRESSES
- OUTER v4 ADDRESSES
- OUTER v6 ADDRESSES
2. IPv4 INNER ADDRESSES with options
- OUTER v4 ADDRESSES
- OUTER v6 ADDRESSES
3. IPv6 INNER ADDRESSES
- OUTER v4 ADDRESSES
- OUTER v6 ADDRESSES
With this patchset, an esp beet mode skb would be segmented and
encryped until it arrives in dev_queue_xmit()/validate_xmit_skb().
Xin Long (3):
esp4: add gso_segment for esp4 beet mode
esp6: add gso_segment for esp6 beet mode
xfrm: add prep for esp beet mode offload
net/ipv4/esp4_offload.c | 32 ++++++++++++++++++++++++++++++++
net/ipv6/esp6_offload.c | 36 ++++++++++++++++++++++++++++++++++++
net/xfrm/xfrm_device.c | 28 +++++++++++++++++++++++++++-
3 files changed, 95 insertions(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2020-03-26 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 9:02 Xin Long [this message]
2020-03-26 9:02 ` [PATCH ipsec-next 1/3] esp4: add gso_segment for esp4 beet mode Xin Long
2020-03-26 9:02 ` [PATCH ipsec-next 2/3] esp6: add gso_segment for esp6 " Xin Long
2020-03-26 9:02 ` [PATCH ipsec-next 3/3] xfrm: add prep for esp beet mode offload Xin Long
2020-03-27 7:51 ` [PATCH ipsec-next 0/3] xfrm: add offload support for esp beet mode Steffen Klassert
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=cover.1585213292.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=steffen.klassert@secunet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.