linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Liam R. Howlett" <Liam.Howlett@Oracle.com>
To: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Cc: Suren Baghdasaryan <surenb@google.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	paulmck@kernel.org, David Rientjes <rientjes@google.com>,
	Joel Fernandes <joelaf@google.com>,
	Lorenzo Stoakes <lstoakes@gmail.com>
Subject: Re: [LSF/MM/BPF TOPIC] Enhancements to RCU-protected VMA walks
Date: Mon, 22 Jan 2024 11:34:11 -0500	[thread overview]
Message-ID: <20240122163411.lcniz2djjy7j5pmk@revolver> (raw)
In-Reply-To: <20240119164227.iiwibb2o6z7hvokq@revolver>


Added Cc's

* Liam R. Howlett <Liam.Howlett@Oracle.com> [240119 11:42]:
> 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.

Thanks to Suren for this [1] work, I should have included the reference
in the first email.  There are more patch sets that increases the impact
of the locks, but I believe v4 that I've linked is the start of the RCU
use of the maple tree.

> 
> 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.

There are some loose ends left in this work that we're still discussing
and working through and I think it would be beneficial to hash some of
it out in person, and have a wider audience exposure.

> 
> AKA: The annual mmap_sem/mmap_lock talk - And this time we mean it!
> 

[1] https://lore.kernel.org/linux-mm/20230227173632.3292573-1-surenb@google.com/


      reply	other threads:[~2024-01-22 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 16:42 Liam R. Howlett
2024-01-22 16:34 ` Liam R. Howlett [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=20240122163411.lcniz2djjy7j5pmk@revolver \
    --to=liam.howlett@oracle.com \
    --cc=joelaf@google.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=lstoakes@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=rientjes@google.com \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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