From: Steffen Klassert <steffen.klassert@secunet.com>
To: <ilant@mellanox.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/7] IPSec offload improvements
Date: Thu, 3 Aug 2017 13:02:41 +0200 [thread overview]
Message-ID: <20170803110241.GJ2631@secunet.com> (raw)
In-Reply-To: <20170801094910.14895-1-ilant@mellanox.com>
On Tue, Aug 01, 2017 at 12:49:03PM +0300, ilant@mellanox.com wrote:
> From: Ilan Tayari <ilant@mellanox.com>
>
> Hi Steffen,
>
> This patchset introduces several improvements to IPSec offload.
> We would like to see these merged in 4.14.
>
> Patches 1-4 add RX checksum offload support.
> This gives a big performance boost.
> These patches have been submitted before but were not merged.
> Note that patches 1-2 changed slightly with a call to skb_pull_rcsum.
>
> Patch 5 adds automatic loading of XFRM offload modules, but only
> if crypto-offload is explicitly requested by user.
> This avoid issues in the field where user forgets to load the
> module manually and so crypto-offload does not happen.
>
> Patch 6 fixes the leftover xfrm_offload in RX SKBs.
> This solves some issues with forwarding.
>
> Patch 7 allows IPSec GSO on local sockets, with or without
> crypto-offload.
> This also gives a large performance boost.
>
> Thanks,
> Ilan.
>
> Ilan Tayari (4):
> esp4: Support RX checksum with crypto offload
> esp6: Support RX checksum with crypto offload
> xfrm: Auto-load xfrm offload modules
> xfrm: Clear RX SKB secpath xfrm_offload
>
> Steffen Klassert (1):
> net: Allow IPsec GSO for local sockets
>
> Yossi Kuperman (2):
> xfrm6: Fix CHECKSUM_COMPLETE after IPv6 header push
> esp6: Fix RX checksum after header pull
All applied to ipsec-next, thanks a lot!
prev parent reply other threads:[~2017-08-03 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 9:49 [PATCH net-next 0/7] IPSec offload improvements ilant
2017-08-01 9:49 ` [PATCH net-next 1/7] esp4: Support RX checksum with crypto offload ilant
2017-08-01 9:49 ` [PATCH net-next 2/7] esp6: " ilant
2017-08-01 9:49 ` [PATCH net-next 3/7] xfrm6: Fix CHECKSUM_COMPLETE after IPv6 header push ilant
2017-08-01 9:49 ` [PATCH net-next 4/7] esp6: Fix RX checksum after header pull ilant
2017-08-01 9:49 ` [PATCH net-next 5/7] xfrm: Auto-load xfrm offload modules ilant
2017-08-01 9:49 ` [PATCH net-next 6/7] xfrm: Clear RX SKB secpath xfrm_offload ilant
2017-08-01 9:49 ` [PATCH net-next 7/7] net: Allow IPsec GSO for local sockets ilant
2017-08-03 11:02 ` 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=20170803110241.GJ2631@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=ilant@mellanox.com \
--cc=netdev@vger.kernel.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