From: Tariq Toukan <tariqt@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: <netdev@vger.kernel.org>, Saeed Mahameed <saeedm@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: [PATCH net V2 0/7] mlx5 fixes 2024-06-27
Date: Thu, 27 Jun 2024 21:02:33 +0300 [thread overview]
Message-ID: <20240627180240.1224975-1-tariqt@nvidia.com> (raw)
Hi,
This patchset provides fixes from the team to the mlx5 core and EN
drivers.
The first 3 patches by Daniel replace a buggy cap field with a newly
introduced one.
Patch 4 by Chris de-couples ingress ACL creation from a specific flow,
so it's invoked by other flows if needed.
Patch 5 by Jianbo fixes a possible missing cleanup of QoS objects.
Patches 6 and 7 by Leon fixes IPsec stats logic to better reflect the
traffic.
Series generated against:
commit 02ea312055da ("octeontx2-pf: Fix coverity and klockwork issues in octeon PF driver")
Regards,
Tariq
V2:
Fixed wrong cited SHA in patch 6.
Chris Mi (1):
net/mlx5: E-switch, Create ingress ACL when needed
Daniel Jurgens (3):
net/mlx5: IFC updates for changing max EQs
net/mlx5: Use max_num_eqs_24b capability if set
net/mlx5: Use max_num_eqs_24b when setting max_io_eqs
Jianbo Liu (1):
net/mlx5e: Add mqprio_rl cleanup and free in mlx5e_priv_cleanup()
Leon Romanovsky (2):
net/mlx5e: Present succeeded IPsec SA bytes and packet
net/mlx5e: Approximate IPsec per-SA payload data bytes count
.../mellanox/mlx5/core/en_accel/ipsec.c | 48 ++++++++++++++-----
.../net/ethernet/mellanox/mlx5/core/en_main.c | 5 ++
drivers/net/ethernet/mellanox/mlx5/core/eq.c | 4 +-
.../mellanox/mlx5/core/esw/acl/ingress_ofld.c | 37 ++++++++++----
.../mellanox/mlx5/core/eswitch_offloads.c | 22 +++++++--
.../ethernet/mellanox/mlx5/core/mlx5_core.h | 10 ++++
.../net/ethernet/mellanox/mlx5/core/pci_irq.c | 4 +-
include/linux/mlx5/mlx5_ifc.h | 6 ++-
8 files changed, 103 insertions(+), 33 deletions(-)
--
2.31.1
next reply other threads:[~2024-06-27 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 18:02 Tariq Toukan [this message]
2024-06-27 18:02 ` [PATCH net V2 1/7] net/mlx5: IFC updates for changing max EQs Tariq Toukan
2024-06-30 7:30 ` Tariq Toukan
2024-06-27 18:02 ` [PATCH net V2 2/7] net/mlx5: Use max_num_eqs_24b capability if set Tariq Toukan
2024-06-27 18:02 ` [PATCH net V2 3/7] net/mlx5: Use max_num_eqs_24b when setting max_io_eqs Tariq Toukan
2024-06-27 18:02 ` [PATCH net V2 4/7] net/mlx5: E-switch, Create ingress ACL when needed Tariq Toukan
2024-06-27 18:02 ` [PATCH net V2 5/7] net/mlx5e: Add mqprio_rl cleanup and free in mlx5e_priv_cleanup() Tariq Toukan
2024-06-27 18:02 ` [PATCH net V2 6/7] net/mlx5e: Present succeeded IPsec SA bytes and packet Tariq Toukan
2024-06-27 18:02 ` [PATCH net V2 7/7] net/mlx5e: Approximate IPsec per-SA payload data bytes count Tariq Toukan
2024-06-28 12:00 ` [PATCH net V2 0/7] mlx5 fixes 2024-06-27 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=20240627180240.1224975-1-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--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 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).