From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, jiri@resnulli.us,
leonro@nvidia.com, saeedm@nvidia.com, idosch@idosch.org,
michael.chan@broadcom.com, simon.horman@corigine.com
Subject: Re: [PATCH net-next v2 0/5] devlink: hold the instance lock in eswitch callbacks
Date: Mon, 21 Mar 2022 16:50:10 +0000 [thread overview]
Message-ID: <164788141087.8756.4036477791453541767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220318192344.1587891-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 18 Mar 2022 12:23:39 -0700 you wrote:
> Series number 2 in the effort to hold the devlink instance lock
> in call driver callbacks. We have the following drivers using
> this API:
>
> - bnxt, nfp, netdevsim - their own locking is removed / simplified
> by this series; all of them needed a lock to protect from changes
> to the number of VFs while switching modes, now the VF config bus
> callback takes the devlink instance lock via devl_lock();
> - ice - appears not to allow changing modes while SR-IOV enabled,
> so nothing to do there;
> - liquidio - does not contain any locking;
> - octeontx2/af - is very special but at least doesn't have locking
> so doesn't get in the way either;
> - mlx5 has a wealth of locks - I chickened out and dropped the lock
> in the callbacks so that I can leave the driver be, for now.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] bnxt: use the devlink instance lock to protect sriov
https://git.kernel.org/netdev/net-next/c/7a1b0b1a555e
- [net-next,v2,2/5] devlink: add explicitly locked flavor of the rate node APIs
https://git.kernel.org/netdev/net-next/c/8879b32a3a80
- [net-next,v2,3/5] netdevsim: replace port_list_lock with devlink instance lock
https://git.kernel.org/netdev/net-next/c/76eea6c2e663
- [net-next,v2,4/5] netdevsim: replace vfs_lock with devlink instance lock
https://git.kernel.org/netdev/net-next/c/aff3a9250946
- [net-next,v2,5/5] devlink: hold the instance lock during eswitch_mode callbacks
https://git.kernel.org/netdev/net-next/c/14e426bf1a4d
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:[~2022-03-21 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 19:23 [PATCH net-next v2 0/5] devlink: hold the instance lock in eswitch callbacks Jakub Kicinski
2022-03-18 19:23 ` [PATCH net-next v2 1/5] bnxt: use the devlink instance lock to protect sriov Jakub Kicinski
2022-03-18 19:23 ` [PATCH net-next v2 2/5] devlink: add explicitly locked flavor of the rate node APIs Jakub Kicinski
2022-03-18 19:23 ` [PATCH net-next v2 3/5] netdevsim: replace port_list_lock with devlink instance lock Jakub Kicinski
2022-03-18 19:23 ` [PATCH net-next v2 4/5] netdevsim: replace vfs_lock " Jakub Kicinski
2022-03-18 19:23 ` [PATCH net-next v2 5/5] devlink: hold the instance lock during eswitch_mode callbacks Jakub Kicinski
2022-03-21 16:50 ` 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=164788141087.8756.4036477791453541767.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.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).