From: Leon Romanovsky <leon@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Steffen Klassert <steffen.klassert@secunet.com>,
Eric Dumazet <edumazet@google.com>,
Jianbo Liu <jianbol@nvidia.com>, Paul Blakey <paulb@nvidia.com>,
Raed Salem <raeds@nvidia.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
Simon Horman <simon.horman@corigine.com>
Subject: [PATCH net 0/3] mlx5 IPsec fixes
Date: Mon, 31 Jul 2023 14:58:39 +0300 [thread overview]
Message-ID: <cover.1690803944.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Hi,
The following patches are combination of Jianbo's work on IPsec eswitch mode
together with our internal review toward addition of TCP protocol selectors
support to IPSec packet offload.
Despite not-being fix, the first patch helps us to make second one more
clear, so I'm asking to apply it anyway as part of this series.
Thanks
Jianbo Liu (2):
net/mlx5: fs_core: Make find_closest_ft more generic
net/mlx5: fs_core: Skip the FTs in the same FS_TYPE_PRIO_CHAINS
fs_prio
Leon Romanovsky (1):
net/mlx5e: Set proper IPsec source port in L4 selector
.../mellanox/mlx5/core/en_accel/ipsec_fs.c | 4 +-
.../net/ethernet/mellanox/mlx5/core/fs_core.c | 103 ++++++++++++++----
2 files changed, 85 insertions(+), 22 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-31 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 11:58 Leon Romanovsky [this message]
2023-07-31 11:58 ` [PATCH net 1/3] net/mlx5: fs_core: Make find_closest_ft more generic Leon Romanovsky
2023-07-31 11:58 ` [PATCH net 2/3] net/mlx5: fs_core: Skip the FTs in the same FS_TYPE_PRIO_CHAINS fs_prio Leon Romanovsky
2023-07-31 11:58 ` [PATCH net 3/3] net/mlx5e: Set proper IPsec source port in L4 selector Leon Romanovsky
2023-08-03 1:50 ` [PATCH net 0/3] mlx5 IPsec fixes patchwork-bot+netdevbpf
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.1690803944.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulb@nvidia.com \
--cc=raeds@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.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).