From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "paulmck@kernel.org" <paulmck@kernel.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [LSF/MM/BPF TOPIC] Changes in RCU over the past few years
Date: Mon, 7 Mar 2022 03:50:43 +0000 [thread overview]
Message-ID: <d25f8c3e-e0d6-cc1c-49ed-7357138aebc3@nvidia.com> (raw)
In-Reply-To: <20220304035116.GA8858@paulmck-ThinkPad-P17-Gen-1>
On 3/3/22 19:51, Paul E. McKenney wrote:
> Hello!
>
> There have been a number of changes to RCU over the past few years,
> including consolidating the update-side RCU-preempt, RCU-sched,
> and RCU-bh flavors, the addition of TREE SRCU, non-sleeping polled
> grace-period interfaces for RCU and SRCU, and addition of a couple
> variants of Tasks RCU. This topic would include a quick overview of
> these changes, with special attention to challenges when back porting to
> pre-consolidated-RCU kernels. Time permitting, it might also be useful
> to look at some of the nuances of SLAB_DESTROY_BY_RCU.
>
> This would also be an opportunity to discuss RCU use cases and potential
> changes to RCU itself.
>
> Thanx, Paul
>
I'll be very much interested in this topic and I think everyone
non-only mm but fs/storage tracks can also benefit from this.
Perhaps we should add respective mailing list to this thread ?
(linux-block and linux-fsdevel)
-ck
next prev parent reply other threads:[~2022-03-07 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 3:51 Paul E. McKenney
2022-03-07 3:50 ` Chaitanya Kulkarni [this message]
2022-03-09 21:38 ` Paul E. McKenney
2022-03-15 5:58 ` Chaitanya Kulkarni
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=d25f8c3e-e0d6-cc1c-49ed-7357138aebc3@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--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