From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: "Paul E. McKenney" <paulmck@linux.ibm.com>
Subject: [Ksummit-discuss] [TECH TOPIC] Concurrency with tools/memory-model/
Date: Sat, 22 Sep 2018 15:34:27 +0200 [thread overview]
Message-ID: <20180922133427.GA3998@andrea> (raw)
Hi all,
Paul E. McKenney and myself would like to propose the following topic
for the technical track.
---
Concurrency is "tricky", it has been said, due to numerous optimizations
implemented in today's multiprocessors and by the compiler.
Traditionally, developers have relied on informal documentation such as
memory-barriers.txt to avoid the "pitfalls of concurrency".
However, this doesn't always happen right: this documentation is subject
of misinterpretations, incomplete, and yet all but concise!
This talk will go over a new approach to study concurrency issues in the
kernel using the Linux-kernel memory consistency model [1].
What can this model do? and, most importantly, how can it be used? This
hands-on talk aims at addressing these questions.
[1] 1c27b644c0fdbc ("Automate memory-barriers.txt; provide Linux-kernel memory model")
---
Thanks,
Andrea
reply other threads:[~2018-09-22 13:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180922133427.GA3998@andrea \
--to=andrea.parri@amarulasolutions.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=paulmck@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.