From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"paulmck@kernel.org" <paulmck@kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] Changes in RCU over the past few years
Date: Tue, 15 Mar 2022 05:58:26 +0000 [thread overview]
Message-ID: <42a52088-4e8f-a0bd-a4e7-0efcd214f075@nvidia.com> (raw)
In-Reply-To: <20220309213845.GG4285@paulmck-ThinkPad-P17-Gen-1>
On 3/9/22 13:38, Paul E. McKenney wrote:
> On Mon, Mar 07, 2022 at 03:50:43AM +0000, Chaitanya Kulkarni wrote:
>> 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)
>
> Works for me!
>
> Thanx, Paul
>
adding linux-block, linux-nvme and linux-fsdevel.
-ck
prev parent reply other threads:[~2022-03-15 5:58 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
2022-03-09 21:38 ` Paul E. McKenney
2022-03-15 5:58 ` Chaitanya Kulkarni [this message]
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=42a52088-4e8f-a0bd-a4e7-0efcd214f075@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.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