From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, idosch@nvidia.com,
petrm@nvidia.com, pabeni@redhat.com, edumazet@google.com,
mlxsw@nvidia.com, saeedm@nvidia.com, tariqt@nvidia.com,
leon@kernel.org, moshe@nvidia.com
Subject: Re: [patch net-next 4/4] net: devlink: enable parallel ops on netlink interface
Date: Mon, 22 Aug 2022 14:26:33 +0200 [thread overview]
Message-ID: <YwN1+YZg1OyE4DXp@nanopsycho> (raw)
In-Reply-To: <20220820124459.44bf1677@kernel.org>
Sat, Aug 20, 2022 at 09:44:59PM CEST, kuba@kernel.org wrote:
>On Fri, 29 Jul 2022 09:10:38 +0200 Jiri Pirko wrote:
>> From: Jiri Pirko <jiri@nvidia.com>
>>
>> As the devlink_mutex was removed and all devlink instances are protected
>> individually by devlink->lock mutex, allow the netlink ops to run
>> in parallel and therefore allow user to execute commands on multiple
>> devlink instances simultaneously.
>
>Could you update the "Locking" section of
>Documentation/networking/devlink/index.rst
>with the full info and recommendations?
Will do.
next prev parent reply other threads:[~2022-08-22 12:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 7:10 [patch net-next 0/4] net: devlink: allow parallel commands on multiple devlinks Jiri Pirko
2022-07-29 7:10 ` [patch net-next 1/4] net: devlink: introduce "unregistering" mark and use it during devlinks iteration Jiri Pirko
2022-07-29 7:10 ` [patch net-next 2/4] net: devlink: convert reload command to take implicit devlink->lock Jiri Pirko
2022-08-05 16:21 ` Keller, Jacob E
2022-08-05 19:58 ` Jakub Kicinski
2022-08-05 20:12 ` Keller, Jacob E
2022-07-29 7:10 ` [patch net-next 3/4] net: devlink: remove devlink_mutex Jiri Pirko
2022-07-29 7:10 ` [patch net-next 4/4] net: devlink: enable parallel ops on netlink interface Jiri Pirko
2022-08-20 19:44 ` Jakub Kicinski
2022-08-22 12:26 ` Jiri Pirko [this message]
2022-07-30 3:04 ` [patch net-next 0/4] net: devlink: allow parallel commands on multiple devlinks Jakub Kicinski
2022-07-30 9:26 ` Jiri Pirko
2022-07-30 15:53 ` Ido Schimmel
2022-07-31 6:02 ` Ido Schimmel
2022-08-01 11:40 ` 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=YwN1+YZg1OyE4DXp@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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