From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Raed Salem <raeds@nvidia.com>,
ipsec-devel <devel@linux-ipsec.org>
Subject: [PATCH xfrm-next 00/26] mlx5 IPsec full offload part
Date: Tue, 16 Aug 2022 13:37:48 +0300 [thread overview]
Message-ID: <cover.1660641154.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Hi,
This is supplementary part of "Extend XFRM core to allow full offload configuration"
series https://lore.kernel.org/all/cover.1660639789.git.leonro@nvidia.com
The series starts from very basic cleanup, continues with code alignment and
adds IPsec full offload logic to mlx5 driver.
Thanks
Leon Romanovsky (25):
net/mlx5: Delete esp_id field that is not used
net/mlx5: Add HW definitions for IPsec full offload
net/mlx5: Remove from FPGA IFC file not-needed definitions
net/mlx5e: Advertise IPsec full offload support
net/mlx5e: Store replay window in XFRM attributes
net/mlx5e: Remove extra layers of defines
net/mlx5e: Create symmetric IPsec RX and TX flow steering structs
net/mlx5e: Use mlx5 print routines for low level IPsec code
net/mlx5e: Remove accesses to priv for low level IPsec FS code
net/mlx5e: Validate that IPsec full offload can handle packets
net/mlx5e: Create Advanced Steering Operation object for IPsec
net/mlx5e: Create hardware IPsec full offload objects
net/mlx5e: Move IPsec flow table creation to separate function
net/mlx5e: Refactor FTE setup code to be more clear
net/mlx5e: Flatten the IPsec RX add rule path
net/mlx5e: Make clear what IPsec rx_err does
net/mlx5e: Group IPsec miss handles into separate struct
net/mlx5e: Generalize creation of default IPsec miss group and rule
net/mlx5e: Create IPsec policy offload tables
net/mlx5e: Add XFRM policy offload logic
net/mlx5e: Use same coding pattern for Rx and Tx flows
net/mlx5e: Configure IPsec full offload flow steering
net/mlx5e: Improve IPsec flow steering autogroup
net/mlx5e: Skip IPsec encryption for TX path without matching policy
net/mlx5e: Open mlx5 driver to accept IPsec full offload
Raed Salem (1):
net/mlx5e: Add statistics for Rx/Tx IPsec offloaded flows
.../net/ethernet/mellanox/mlx5/core/en/fs.h | 3 +-
.../mellanox/mlx5/core/en_accel/ipsec.c | 209 +++-
.../mellanox/mlx5/core/en_accel/ipsec.h | 93 +-
.../mellanox/mlx5/core/en_accel/ipsec_fs.c | 1066 ++++++++++++-----
.../mlx5/core/en_accel/ipsec_offload.c | 81 +-
.../mellanox/mlx5/core/en_accel/ipsec_stats.c | 52 +
.../ethernet/mellanox/mlx5/core/en_stats.c | 1 +
.../ethernet/mellanox/mlx5/core/en_stats.h | 1 +
.../net/ethernet/mellanox/mlx5/core/fs_core.c | 6 +-
include/linux/mlx5/fs.h | 5 +-
include/linux/mlx5/mlx5_ifc.h | 71 +-
include/linux/mlx5/mlx5_ifc_fpga.h | 24 -
12 files changed, 1223 insertions(+), 389 deletions(-)
--
2.37.2
next reply other threads:[~2022-08-16 11:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 10:37 Leon Romanovsky [this message]
2022-08-16 10:37 ` [PATCH xfrm-next 01/26] net/mlx5: Delete esp_id field that is not used Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 02/26] net/mlx5: Add HW definitions for IPsec full offload Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 03/26] net/mlx5: Remove from FPGA IFC file not-needed definitions Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 04/26] net/mlx5e: Advertise IPsec full offload support Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 05/26] net/mlx5e: Store replay window in XFRM attributes Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 06/26] net/mlx5e: Remove extra layers of defines Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 07/26] net/mlx5e: Create symmetric IPsec RX and TX flow steering structs Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 08/26] net/mlx5e: Use mlx5 print routines for low level IPsec code Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 09/26] net/mlx5e: Remove accesses to priv for low level IPsec FS code Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 10/26] net/mlx5e: Validate that IPsec full offload can handle packets Leon Romanovsky
2022-08-16 10:37 ` [PATCH xfrm-next 11/26] net/mlx5e: Create Advanced Steering Operation object for IPsec Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 12/26] net/mlx5e: Create hardware IPsec full offload objects Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 13/26] net/mlx5e: Move IPsec flow table creation to separate function Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 14/26] net/mlx5e: Refactor FTE setup code to be more clear Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 15/26] net/mlx5e: Flatten the IPsec RX add rule path Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 16/26] net/mlx5e: Make clear what IPsec rx_err does Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 17/26] net/mlx5e: Group IPsec miss handles into separate struct Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 18/26] net/mlx5e: Generalize creation of default IPsec miss group and rule Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 19/26] net/mlx5e: Create IPsec policy offload tables Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 20/26] net/mlx5e: Add XFRM policy offload logic Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 21/26] net/mlx5e: Use same coding pattern for Rx and Tx flows Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 22/26] net/mlx5e: Configure IPsec full offload flow steering Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 23/26] net/mlx5e: Improve IPsec flow steering autogroup Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 24/26] net/mlx5e: Add statistics for Rx/Tx IPsec offloaded flows Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 25/26] net/mlx5e: Skip IPsec encryption for TX path without matching policy Leon Romanovsky
2022-08-16 10:38 ` [PATCH xfrm-next 26/26] net/mlx5e: Open mlx5 driver to accept IPsec full offload 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.1660641154.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=devel@linux-ipsec.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raeds@nvidia.com \
--cc=saeedm@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).