From: Ido Schimmel <idosch@nvidia.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
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 0/4] net: devlink: allow parallel commands on multiple devlinks
Date: Sat, 30 Jul 2022 18:53:11 +0300 [thread overview]
Message-ID: <YuVT58c3PVkvR+DL@shredder> (raw)
In-Reply-To: <20220729071038.983101-1-jiri@resnulli.us>
On Fri, Jul 29, 2022 at 09:10:34AM +0200, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> Aim of this patchset is to remove devlink_mutex and eventually to enable
> parallel ops on devlink netlink interface.
Will report regression results tomorrow morning.
next prev parent reply other threads:[~2022-07-30 15:53 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
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 [this message]
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=YuVT58c3PVkvR+DL@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.