From: "Liam R. Howlett" <Liam.Howlett@Oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [LSF/MM/BPF TOPIC] Scalable Pagefaults
Date: Wed, 22 Feb 2023 13:36:55 -0500 [thread overview]
Message-ID: <20230222183655.swfsssw63m7z3ktq@revolver> (raw)
In-Reply-To: <Y+/f9slIaK195fRX@casper.infradead.org>
* Matthew Wilcox <willy@infradead.org> [230217 15:14]:
> We should continue the conversation from last year on the topic of page
> fault scalability. I presume that by the time of the conference Suren's
> current patches for per-VMA locks [1] [2] will be at least in Andrew's
> tree, even if not quite upstream yet. We will then be in a good place
> to discuss enhancements:
>
> - File-backed VMAs
> - UFFD
> - Swap
> - Improve performance for low-thread-count apps
> - Full RCU handling of (some) page faults
A few other enhancements that we should discuss:
- Adding protection of detached VMAs to mmap_lock page fault handler
- Using detached VMAs to stop stack expansion and allow mmap_write_lock
to downgrade regardless of surrounding VMAs.
- Fast mmap_write_downgrade by using detached VMAs in other code paths.
>
> Suren Baghdasaryan, Liam Howlett, Michel Lespinasse, Laurent Dufour,
> Peter Xu would all be good participants.
>
> [1] https://lore.kernel.org/linux-mm/20230216051750.3125598-1-surenb@google.com/
> [2] https://lwn.net/Articles/906852/
>
>
prev parent reply other threads:[~2023-02-22 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 20:13 [LSF/MM/BPF TOPIC] Scalable Pagefaults Matthew Wilcox
2023-02-22 18:36 ` 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=20230222183655.swfsssw63m7z3ktq@revolver \
--to=liam.howlett@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).