[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXpAScyRUuI3bH13@shikoro>
Date: Wed, 28 Jan 2026 17:58:49 +0100
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Bartosz Golaszewski <brgl@...nel.org>, Johan Hovold <johan@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Danilo Krummrich <dakr@...nel.org>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Tzung-Bi Shih <tzungbi@...nel.org>,
Linus Walleij <linusw@...nel.org>, Jonathan Corbet <corbet@....net>,
Shuah Khan <shuah@...nel.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Simona Vetter <simona.vetter@...ll.ch>,
Dan Williams <dan.j.williams@...el.com>, linux-doc@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
Subject: Re: [PATCH 0/3] Revert "revocable: Revocable resource management"
> I would just gently advise again that SRCU is not a pancea and should
> only be used if the read side sections are super performance
> critical. I'm not sure that describes I2C. rwsem is often a simpler
> and better choice.
You might be totally right. But in any case, we need to prepare the
subsystem first. That is where I am now. Next steps come after that.
> > [1] https://lkml.org/lkml/2021/1/20/999
>
> Yeah, this was brought up a couple drafts of possible options were
> exchanged already but nothing was really focused on and polished.
>
> It is a tricky problem to find a storage location for the lock and
> revoke so that the fops shim can access it while not disturbing the
> actual driver.
I can imagine. Thanks for the heads up, nice to see it was not
forgotten!
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists