From: "Liam R. Howlett" <Liam.Howlett@Oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM/BPF TOPIC] Enhancements to RCU-protected VMA walks
Date: Fri, 19 Jan 2024 11:42:27 -0500 [thread overview]
Message-ID: <20240119164227.iiwibb2o6z7hvokq@revolver> (raw)
With the introduction of the per-vma locking in the pagefault handler,
the VMA tree is beginning to be used without the mmap_lock taken at all.
I'd like to talk about where we are in the process of RCU-protected VMA
walks, and where we are headed with a discussion around problems which
may arise and some mitigation ideas.
AKA: The annual mmap_sem/mmap_lock talk - And this time we mean it!
next reply other threads:[~2024-01-19 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 16:42 Liam R. Howlett [this message]
2024-01-22 16:34 ` Liam R. Howlett
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=20240119164227.iiwibb2o6z7hvokq@revolver \
--to=liam.howlett@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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