From: patchwork-bot+netdevbpf@kernel•org
To: Tariq Toukan <tariqt@nvidia•com>
Cc: edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
andrew+netdev@lunn•ch, davem@davemloft•net, saeedm@nvidia•com,
leon@kernel•org, mbloch@nvidia•com, netdev@vger•kernel.org,
linux-rdma@vger•kernel.org, linux-kernel@vger•kernel.org,
gal@nvidia•com, dtatulea@nvidia•com, cratiu@nvidia•com
Subject: Re: [PATCH net] net/mlx5: Don't zero user_count when destroying FDB tables
Date: Thu, 30 Oct 2025 01:00:14 +0000 [thread overview]
Message-ID: <176178601425.3269431.7440616130656460451.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1761510019-938772-1-git-send-email-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Sun, 26 Oct 2025 22:20:19 +0200 you wrote:
> From: Cosmin Ratiu <cratiu@nvidia•com>
>
> esw->user_count tracks how many TC rules are added on an esw via
> mlx5e_configure_flower -> mlx5_esw_get -> atomic64_inc(&esw->user_count)
>
> esw.user_count was unconditionally set to 0 in
> esw_destroy_legacy_fdb_table and esw_destroy_offloads_fdb_tables.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: Don't zero user_count when destroying FDB tables
https://git.kernel.org/netdev/net/c/53110232c95f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-30 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 20:20 [PATCH net] net/mlx5: Don't zero user_count when destroying FDB tables Tariq Toukan
2025-10-28 16:57 ` Simon Horman
2025-10-30 1:00 ` patchwork-bot+netdevbpf [this message]
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=176178601425.3269431.7440616130656460451.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=cratiu@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dtatulea@nvidia$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=gal@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=mbloch@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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