[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220727190156.0ec856ae@kernel.org>
Date: Wed, 27 Jul 2022 19:01:56 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Moshe Shemesh <moshe@...dia.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Saeed Mahameed <saeedm@...dia.com>,
Leon Romanovsky <leon@...nel.org>,
"Tariq Toukan" <tariqt@...dia.com>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>, Jiri Pirko <jiri@...dia.com>,
<netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 2/9] net: devlink: remove region snapshots list
dependency on devlink->lock
On Wed, 27 Jul 2022 20:03:29 +0300 Moshe Shemesh wrote:
> From: Jiri Pirko <jiri@...dia.com>
>
> After mlx4 driver is converted to do locked reload,
> devlink_region_snapshot_create() may be called from both locked and
> unlocked context.
You need to explain why, tho. What makes region snapshots special?
> So resolve this by removing dependency on devlink->lock for region
> snapshots list consistency and introduce new mutex to ensure it.
I was hoping to avoid per-subobject locks. What prevents us from
depending on the instance lock here (once the driver is converted)?
Powered by blists - more mailing lists