From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Saeed Mahameed <saeedm@nvidia.com>,
linux-netdev <netdev@vger.kernel.org>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: [GIT PULL] Please pull mlx5-next changes
Date: Wed, 15 Feb 2023 11:56:24 +0200 [thread overview]
Message-ID: <20230215095624.1365200-1-leon@kernel.org> (raw)
Hi Jason,
Following previous conversations [1] and our clear commitment to do the TC work [2],
please pull mlx5-next shared branch, which includes low-level steering logic to allow
RoCEv2 traffic to be encrypted/decrypted through IPsec.
Thanks
[1] https://lore.kernel.org/all/20230126230815.224239-1-saeed@kernel.org/
[2] https://lore.kernel.org/all/Y+Z7lVVWqnRBiPh2@nvidia.com/
----------------------------------------------------------------
The following changes since commit dca55da0a15717dde509d17163946e951bad56c4:
RDMA/mlx5: Track netdev to avoid deadlock during netdev notifier unregister (2023-02-08 20:40:57 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/ mlx5-next
for you to fetch changes up to 22551e77e5507a06114c0af2b92bbf1a66ec33c5:
net/mlx5: Configure IPsec steering for egress RoCEv2 traffic (2023-02-15 11:30:07 +0200)
----------------------------------------------------------------
Mark Zhang (4):
net/mlx5: Implement new destination type TABLE_TYPE
net/mlx5: Add IPSec priorities in RDMA namespaces
net/mlx5: Configure IPsec steering for ingress RoCEv2 traffic
net/mlx5: Configure IPsec steering for egress RoCEv2 traffic
Patrisious Haddad (1):
net/mlx5: Introduce new destination type TABLE_TYPE
drivers/net/ethernet/mellanox/mlx5/core/Makefile | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/diag/fs_tracepoint.c | 4 +
drivers/net/ethernet/mellanox/mlx5/core/en/fs.h | 1 +
drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.h | 2 +
drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec_fs.c | 54 ++++++-
drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec_offload.c | 5 +
drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c | 6 +
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c | 44 +++++-
drivers/net/ethernet/mellanox/mlx5/core/lib/ipsec_fs_roce.c | 368 +++++++++++++++++++++++++++++++++++++++++++++
drivers/net/ethernet/mellanox/mlx5/core/lib/ipsec_fs_roce.h | 25 +++
include/linux/mlx5/fs.h | 3 +
include/linux/mlx5/mlx5_ifc.h | 12 +-
12 files changed, 511 insertions(+), 15 deletions(-)
create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/lib/ipsec_fs_roce.c
create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/lib/ipsec_fs_roce.h
next reply other threads:[~2023-02-15 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 9:56 Leon Romanovsky [this message]
2023-02-16 19:37 ` [GIT PULL] Please pull mlx5-next changes Jakub Kicinski
2023-02-19 9:05 ` Leon Romanovsky
2023-02-16 19:40 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-04-09 5:53 Leon Romanovsky
2022-04-12 3:50 ` patchwork-bot+netdevbpf
2022-04-12 13:57 ` Jason Gunthorpe
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=20230215095624.1365200-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.