From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Boqun Feng <boqun.feng@gmail.com>, paulmck <paulmck@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hazard pointer enabled refcount prototype
Date: Sat, 5 Oct 2024 10:43:04 +0200 [thread overview]
Message-ID: <2024100538-acquire-imprecise-ecee@gregkh> (raw)
In-Reply-To: <3b749585-1286-4a4e-acd0-1534b60172da@efficios.com>
On Fri, Oct 04, 2024 at 03:52:01PM -0400, Mathieu Desnoyers wrote:
> Hi Greg,
>
> After our discussion at KR2024, I've created a prototype adding hazard pointer
> dereference support to refcount.h:
>
> https://github.com/compudj/linux-dev/commit/234523dc9be90f1bc9221bf2d430c9187ac61528
>
> Branch: https://github.com/compudj/linux-dev/tree/hp-6.11-refcount
>
> It allows dereferencing a pointer to a refcount and incrementing the refcount,
> without relying on RCU.
>
> A good candidate for this would be the "usblp" driver which is using a static mutex
> for existence guarantees. Introducing a refcount as first field of struct usblp
> should do the trick.
>
> I am not entirely sure if this kind of use-case justifies introducing hazard pointers
> though, as this can be done just as well with RCU. I'll let you be the judge on this.
How could it be used with RCU? I'll have to look into that, but thanks
for the links and I'll dig into this on Monday to see if I could use
these to get rid of the "static mutex" pattern that almost all drivers
need to have these days (which in turn will mean we will not need to use
that in new rust drivers either, which will make them simpler as well
because the static mutex pattern in rust is rough to make work.)
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-05 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 19:52 Hazard pointer enabled refcount prototype Mathieu Desnoyers
2024-10-05 8:43 ` Greg Kroah-Hartman [this message]
2024-10-05 15:01 ` Mathieu Desnoyers
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=2024100538-acquire-imprecise-ecee@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
/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