From: patchwork-bot+netdevbpf@kernel.org
To: Shay Drory <shayd@nvidia.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
kuba@kernel.org, edumazet@google.com, jiri@nvidia.com
Subject: Re: [PATCH net v2] devlink: Fix devlink parallel commands processing
Date: Wed, 13 Mar 2024 08:40:29 +0000 [thread overview]
Message-ID: <171031922942.8351.16226368528415050004.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240312105238.296278-1-shayd@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 12 Mar 2024 12:52:38 +0200 you wrote:
> Commit 870c7ad4a52b ("devlink: protect devlink->dev by the instance
> lock") added devlink instance locking inside a loop that iterates over
> all the registered devlink instances on the machine in the pre-doit
> phase. This can lead to serialization of devlink commands over
> different devlink instances.
>
> For example: While the first devlink instance is executing firmware
> flash, all commands to other devlink instances on the machine are
> forced to wait until the first devlink finishes.
>
> [...]
Here is the summary with links:
- [net,v2] devlink: Fix devlink parallel commands processing
https://git.kernel.org/netdev/net/c/d7d75124965a
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:[~2024-03-13 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 10:52 [PATCH net v2] devlink: Fix devlink parallel commands processing Shay Drory
2024-03-12 12:13 ` Jiri Pirko
2024-03-13 8:40 ` 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=171031922942.8351.16226368528415050004.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shayd@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).