From: ilant@mellanox.com
To: Steffen Klassert <steffen.klassert@secunet.com>, netdev@vger.kernel.org
Cc: Ilan Tayari <ilant@mellanox.com>
Subject: [PATCH net-next 0/7] IPSec offload improvements
Date: Tue, 1 Aug 2017 12:49:03 +0300 [thread overview]
Message-ID: <20170801094910.14895-1-ilant@mellanox.com> (raw)
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
include/net/xfrm.h | 23 ++++++++++++++++++++++-
net/core/sock.c | 2 +-
net/ipv4/esp4.c | 14 +++++++++++---
net/ipv4/esp4_offload.c | 5 ++++-
net/ipv6/esp6.c | 16 +++++++++++++---
net/ipv6/esp6_offload.c | 5 ++++-
net/ipv6/xfrm6_input.c | 4 +++-
net/xfrm/xfrm_device.c | 2 +-
net/xfrm/xfrm_input.c | 2 ++
net/xfrm/xfrm_state.c | 16 ++++++++++++----
net/xfrm/xfrm_user.c | 2 +-
11 files changed, 74 insertions(+), 17 deletions(-)
--
2.11.0
next reply other threads:[~2017-08-01 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 9:49 ilant [this message]
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 ` [PATCH net-next 0/7] IPSec offload improvements 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=20170801094910.14895-1-ilant@mellanox.com \
--to=ilant@mellanox.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox