From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, Raed Salem <raeds@nvidia.com>,
ipsec-devel <devel@linux-ipsec.org>
Subject: [PATCH ipsec-next v1 0/6] Extend XFRM core to allow full offload configuration
Date: Wed, 18 May 2022 08:30:20 +0300 [thread overview]
Message-ID: <cover.1652851393.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Changelog:
v1: Moved comment to be before if (...) in third patch.
v0: https://lore.kernel.org/all/cover.1652176932.git.leonro@nvidia.com
-----------------------------------------------------------------------
The following series extends XFRM core code to handle new type of IPsec
offload - full offload.
In this mode, the HW is going to be responsible for whole data path, so
both policy and state should be offloaded.
Thanks
Leon Romanovsky (6):
xfrm: add new full offload flag
xfrm: allow state full offload mode
xfrm: add an interface to offload policy
xfrm: add TX datapath support for IPsec full offload mode
xfrm: add RX datapath protection for IPsec full offload mode
xfrm: enforce separation between priorities of HW/SW policies
.../inline_crypto/ch_ipsec/chcr_ipsec.c | 4 +
.../net/ethernet/intel/ixgbe/ixgbe_ipsec.c | 5 +
drivers/net/ethernet/intel/ixgbevf/ipsec.c | 5 +
.../mellanox/mlx5/core/en_accel/ipsec.c | 4 +
drivers/net/netdevsim/ipsec.c | 5 +
include/linux/netdevice.h | 3 +
include/net/netns/xfrm.h | 8 +-
include/net/xfrm.h | 102 ++++++++++++----
include/uapi/linux/xfrm.h | 6 +
net/xfrm/xfrm_device.c | 84 ++++++++++++-
net/xfrm/xfrm_output.c | 19 +++
net/xfrm/xfrm_policy.c | 115 ++++++++++++++++++
net/xfrm/xfrm_user.c | 11 ++
13 files changed, 342 insertions(+), 29 deletions(-)
--
2.36.1
next reply other threads:[~2022-05-18 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 5:30 Leon Romanovsky [this message]
2022-05-18 5:30 ` [PATCH ipsec-next v1 1/6] xfrm: add new full offload flag Leon Romanovsky
2022-05-18 5:30 ` [PATCH ipsec-next v1 2/6] xfrm: allow state full offload mode Leon Romanovsky
2022-05-18 5:30 ` [PATCH ipsec-next v1 3/6] xfrm: add an interface to offload policy Leon Romanovsky
2022-05-18 5:30 ` [PATCH ipsec-next v1 4/6] xfrm: add TX datapath support for IPsec full offload mode Leon Romanovsky
2022-05-18 5:30 ` [PATCH ipsec-next v1 5/6] xfrm: add RX datapath protection " Leon Romanovsky
2022-05-18 5:30 ` [PATCH ipsec-next v1 6/6] xfrm: enforce separation between priorities of HW/SW policies Leon Romanovsky
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.1652851393.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=devel@linux-ipsec.org \
--cc=herbert@gondor.apana.org.au \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=raeds@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).