Rust for Linux List
 help / color / mirror / Atom feed
From: "Onur Özkan" <work@onurozkan.dev>
To: Gary Guo <gary@garyguo.net>
Cc: rcu@vger.kernel.org, rust-for-linux@vger.kernel.org,
	linux-kernel@vger.kernel.org, ojeda@kernel.org, boqun@kernel.org,
	bjorn3_gh@protonmail.com, lossin@kernel.org,
	a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
	dakr@kernel.org, peterz@infradead.org, fujita.tomonori@gmail.com,
	tamird@kernel.org, jiangshanlai@gmail.com, paulmck@kernel.org,
	josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com
Subject: Re: [PATCH v8 1/4] rust: helpers: add SRCU helpers
Date: Fri, 29 May 2026 15:30:07 +0300	[thread overview]
Message-ID: <20260529123018.177238-1-work@onurozkan.dev> (raw)
In-Reply-To: <DIV5JADSFZEM.3DV46U1BI4EYS@garyguo.net>

On Fri, 29 May 2026 13:16:17 +0100
Gary Guo <gary@garyguo.net> wrote:

> On Fri May 29, 2026 at 1:07 PM BST, Onur Özkan wrote:
> > On Fri, 29 May 2026 12:58:17 +0100
> > Gary Guo <gary@garyguo.net> wrote:
> >
> >> On Fri May 29, 2026 at 12:43 PM BST, Onur Özkan wrote:
> >> > Add helper wrappers for SRCU functions that are exposed to Rust
> >> > through generated bindings.
> >> >
> >> > Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
> >> > Signed-off-by: Onur Özkan <work@onurozkan.dev>
> >> > ---
> >> >  include/linux/srcu.h   |  5 +++++
> >> >  rust/helpers/helpers.c |  1 +
> >> >  rust/helpers/srcu.c    | 30 ++++++++++++++++++++++++++++++
> >> >  3 files changed, 36 insertions(+)
> >> >  create mode 100644 rust/helpers/srcu.c
> >> >
> >> > diff --git a/include/linux/srcu.h b/include/linux/srcu.h
> >> > index 81b1938512d5..790a4ef713c0 100644
> >> > --- a/include/linux/srcu.h
> >> > +++ b/include/linux/srcu.h
> >> > @@ -57,6 +57,11 @@ int __init_srcu_struct_fast_updown(struct srcu_struct *ssp, const char *name,
> >> >  #else /* #ifdef CONFIG_DEBUG_LOCK_ALLOC */
> >> >  
> >> >  int init_srcu_struct(struct srcu_struct *ssp);
> >> > +static inline int __init_srcu_struct(struct srcu_struct *ssp, const char *name,
> >> > +				     struct lock_class_key *key)
> >> > +{
> >> > +	return init_srcu_struct(ssp);
> >> > +}
> >> 
> >> 
> >> This looks like a different strategy than, say, how mutex handles lockdep. IMO
> >> the way that mutex handles this is more clear.
> >
> > Initially it was the same strategy, this one was suggested by Paul [1] and it
> > didn't sound like a bad idea to me. Also, in previous revisions, Boqun once
> > said:
> 
> I'm talking about changing how this is handled in SRCU side, not helper side.
> 
> >
> > 	"Having a "#ifdef" in a function body is generally considered as bad code
> > 	(I know we have some of these in rust helpers, but helpers are a bit
> > 	special and maybe we should clean them up). So could you move this
> > 	function into include/linux/srcutiny.h and include/linux/srcutree.h?"
> 
> mutex.h doesn't use ifdef inside function body, it just define two static inline
> functions with the same signature in different ifdef branches.
> 

I might have confused them, let me check them again.

Thanks,
Onur

> Best,
> Gary
> 
> >
> > So putting them together, I decided to follow Paul's suggestion.
> >
> > [1]: https://lore.kernel.org/all/05906890-cf06-414c-a625-02f9d7150d57@paulmck-laptop
> >
> >> 
> >> If we follow the way mutex is handles this, the `init_srcu_struct` would always
> >> create lock class key and forward to `__init_srcu_struct`, and
> >> `__init_srcu_struct` is an inline function that either calls
> >> `init_srcu_struct_lockdep` with all args, or discard name/key and forward to
> >> `init_srcu_struct_mutex`.
> >> 
> >> This is beneficial because the usage flows one way. You don't have in one config
> >> `init_srcu_struct` call `__init_srcu_struct` and have the opposite in another
> >> config, which I think can be quite confusing.

  reply	other threads:[~2026-05-29 12:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 11:43 [PATCH v8 0/4] rust: helpers: add SRCU helpers Onur Özkan
2026-05-29 11:43 ` [PATCH v8 1/4] " Onur Özkan
2026-05-29 11:58   ` Gary Guo
2026-05-29 12:07     ` Onur Özkan
2026-05-29 12:16       ` Gary Guo
2026-05-29 12:30         ` Onur Özkan [this message]
2026-05-30 19:01         ` Paul E. McKenney
2026-05-30 19:04           ` Onur Özkan
2026-05-29 11:43 ` [PATCH v8 2/4] srcu: expose srcu_readers_active() Onur Özkan
2026-05-29 11:58   ` Gary Guo
2026-05-29 11:43 ` [PATCH v8 3/4] rust: sync: add SRCU abstraction Onur Özkan
2026-05-29 11:43 ` [PATCH v8 4/4] MAINTAINERS: add Rust SRCU files to SRCU entry Onur Özkan

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=20260529123018.177238-1-work@onurozkan.dev \
    --to=work@onurozkan.dev \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=ojeda@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    /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