From: Joel Fernandes <joel@joelfernandes.org>
To: lsf-pc@lists.linux-foundation.org
Cc: Boqun Feng <boqun.feng@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-mm <linux-mm@kvack.org>, rcu <rcu@vger.kernel.org>
Subject: LSFMMBPF proposal [General/MM]: SRCU: a case study in memory ordering
Date: Wed, 11 Jan 2023 14:43:36 +0000 [thread overview]
Message-ID: <CAEXW_YRfDB8Pqf1ppagF=s-Ks=2DBYb=iVtdHdFSz+F36weBqg@mail.gmail.com> (raw)
Title: SRCU: a case study in memory ordering
Description:
Memory ordering guarantees are the backbone of SRCU, an important RCU
synchronization mechanism in the kernel. Can we use the Linux kernel
memory model to understand complex concurrent code better?
In this talk, we will go over:
- SRCU internals overview and why it works
- Discuss in detail, all the 8 or so memory barriers in SRCU and why
they are needed.
- Comparable access patterns to each barrier (LB, MP etc)
- Linux kernel memory model (LKMM) experiments on studying effects of
each memory barrier, along with execution candidate graphs generated
by herd7.
- Possible formal methods / models.
- Discuss both correctness and forward progress issues tackled by
these memory barriers.
(Resending as my previous email got messed up by mail client, thanks).
- Joel
next reply other threads:[~2023-01-11 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 14:43 Joel Fernandes [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-11 11:32 Joel Fernandes
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='CAEXW_YRfDB8Pqf1ppagF=s-Ks=2DBYb=iVtdHdFSz+F36weBqg@mail.gmail.com' \
--to=joel@joelfernandes.org \
--cc=boqun.feng@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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