From: SeongJae Park <sj@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: SeongJae Park <sj@kernel.org>,
akpm@linux-foundation.org, willy@infradead.org,
paulmck@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mm/slab: break up RCU readers on SLAB_TYPESAFE_BY_RCU example code
Date: Mon, 17 Apr 2023 17:26:57 +0000 [thread overview]
Message-ID: <20230417172657.21925-1-sj@kernel.org> (raw)
In-Reply-To: <e2561303-8853-7e16-7eba-001415d34e09@suse.cz>
Hi Vlastimil,
On Mon, 17 Apr 2023 13:05:40 +0200 Vlastimil Babka <vbabka@suse.cz> wrote:
> On 4/15/23 05:31, SeongJae Park wrote:
> > The SLAB_TYPESAFE_BY_RCU example code snippet is having not tiny RCU
>
> Since "tiny RCU" means something quite specific in the RCU world, it can be
> confusing to read it in this sense. We could say e.g. "... snippet uses a
> single RCU read-side critical section for retries"?
Looks much better, thank you for this suggestion!
>
> > read-side critical section. 'Documentation/RCU/rculist_nulls.rst' has
> > similar example code snippet, and commit da82af04352b ("doc: Update and
> > wordsmith rculist_nulls.rst") has broken it.
>
> "has broken it" has quite different meaning than "has broken it up" :) I
> guess we could just add the "up", unless someone has an even better wording.
Good point, thank you for your suggestion!
I will apply above suggestion on the next spin.
Thanks,
SJ
>
> > Apply the change to
> > SLAB_TYPESAFE_BY_RCU example code snippet, too.
> >
> > Signed-off-by: SeongJae Park <sj@kernel.org>
> > ---
> > include/linux/slab.h | 8 +++++---
> > 1 file changed, 5 insertions(+), 3 deletions(-)
> >
> > diff --git a/include/linux/slab.h b/include/linux/slab.h
> > index b18e56c6f06c..6acf1b7c6551 100644
> > --- a/include/linux/slab.h
> > +++ b/include/linux/slab.h
> > @@ -53,16 +53,18 @@
> > * stays valid, the trick to using this is relying on an independent
> > * object validation pass. Something like:
> > *
> > + * begin:
> > * rcu_read_lock();
> > - * again:
> > * obj = lockless_lookup(key);
> > * if (obj) {
> > * if (!try_get_ref(obj)) // might fail for free objects
> > - * goto again;
> > + * rcu_read_unlock();
> > + * goto begin;
> > *
> > * if (obj->key != key) { // not the object we expected
> > * put_ref(obj);
> > - * goto again;
> > + * rcu_read_unlock();
> > + * goto begin;
> > * }
> > * }
> > * rcu_read_unlock();
>
next prev parent reply other threads:[~2023-04-17 17:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 3:31 [PATCH v2 0/2] mm/slab: trivial fixup for SLAB_TYPESAFE_BY_RCU example code snippet SeongJae Park
2023-04-15 3:31 ` [PATCH v2 1/2] mm/slab: add a missing semicolon on SLAB_TYPESAFE_BY_RCU example code SeongJae Park
2023-04-24 17:43 ` Paul E. McKenney
2023-04-24 18:27 ` Vlastimil Babka
2023-04-24 18:35 ` Paul E. McKenney
2023-04-15 3:31 ` [PATCH v2 2/2] mm/slab: break up RCU readers " SeongJae Park
2023-04-15 3:49 ` Matthew Wilcox
2023-04-15 16:27 ` SeongJae Park
2023-04-17 11:05 ` Vlastimil Babka
2023-04-17 17:26 ` SeongJae Park [this message]
2023-04-17 17:53 ` Matthew Wilcox
2023-04-17 19:01 ` SeongJae Park
2023-04-17 19:02 ` Vlastimil Babka
2023-04-17 19:08 ` SeongJae Park
2023-04-17 19:31 ` Matthew Wilcox
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=20230417172657.21925-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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