From: Steffen Klassert <steffen.klassert@secunet.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: <netdev@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Florian Westphal <fw@strlen.de>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [PATCH ipsec-next 0/3] xfrm: add offload support for esp beet mode
Date: Fri, 27 Mar 2020 08:51:07 +0100 [thread overview]
Message-ID: <20200327075107.GZ13121@gauss3.secunet.de> (raw)
In-Reply-To: <cover.1585213292.git.lucien.xin@gmail.com>
On Thu, Mar 26, 2020 at 05:02:28PM +0800, Xin Long wrote:
> 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
Series applied to ipsec-next, thanks a lot Xin!
prev parent reply other threads:[~2020-03-27 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 9:02 [PATCH ipsec-next 0/3] xfrm: add offload support for esp beet mode Xin Long
2020-03-26 9:02 ` [PATCH ipsec-next 1/3] esp4: add gso_segment for esp4 " 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 ` Steffen Klassert [this message]
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=20200327075107.GZ13121@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).