From: Suren Baghdasaryan <surenb@google.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: Re: [PATCH 0/6] Handle more faults under the VMA lock
Date: Wed, 27 Sep 2023 15:18:38 -0700 [thread overview]
Message-ID: <CAJuCfpE69Cbt7AHL2iQuTU578hP5wi0soOVp6i67QE1SeCrAHQ@mail.gmail.com> (raw)
In-Reply-To: <20230927052505.2855872-1-willy@infradead.org>
On Tue, Sep 26, 2023 at 10:25 PM Matthew Wilcox (Oracle)
<willy@infradead.org> wrote:
>
> At this point, we're handling the majority of file-backed page faults
> under the VMA lock, using the ->map_pages entry point. This patch set
> attempts to expand that for the following siutations:
>
> - We have to do a read. This could be because we've hit the point in
> the readahead window where we need to kick off the next readahead,
> or because the page is simply not present in cache.
> - We're handling a write fault. Most applications don't do I/O by writes
> to shared mmaps for very good reasons, but some do, and it'd be nice
> to not make that slow unnecessarily.
> - We're doing a COW of a private mapping (both PTE already present
> and PTE not-present). These are two different codepaths and I handle
> both of them in this patch set.
>
> There is no support in this patch set for drivers to mark themselves
> as being VMA lock friendly; they could implement the ->map_pages
> vm_operation, but if they do, they would be the first. This is probably
> something we want to change at some point in the future, and I've marked
> where to make that change in the code.
>
> Suren, would you mind dropping this into your benchmarking setup and
> seeing if these relatively minor additions make a difference?
Definitely. Thanks for doing this! I'll report once I have some
numbers but first I need to review the patches to understand which
benchmarks could show the benefit.
>
> Matthew Wilcox (Oracle) (6):
> mm: Make lock_folio_maybe_drop_mmap() VMA lock aware
> mm: Call wp_page_copy() under the VMA lock
> mm: Handle shared faults under the VMA lock
> mm: Handle COW faults under the VMA lock
> mm: Handle read faults under the VMA lock
> mm: Handle write faults to RO pages under the VMA lock
>
> mm/filemap.c | 13 ++++----
> mm/memory.c | 93 ++++++++++++++++++++++++++++++++--------------------
> 2 files changed, 65 insertions(+), 41 deletions(-)
>
> --
> 2.40.1
>
prev parent reply other threads:[~2023-09-27 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 5:24 Matthew Wilcox (Oracle)
2023-09-27 5:24 ` [PATCH 1/6] mm: Make lock_folio_maybe_drop_mmap() VMA lock aware Matthew Wilcox (Oracle)
2023-09-27 5:25 ` [PATCH 2/6] mm: Call wp_page_copy() under the VMA lock Matthew Wilcox (Oracle)
2023-09-27 22:38 ` Suren Baghdasaryan
2023-09-28 5:18 ` Matthew Wilcox
2023-09-28 14:57 ` Suren Baghdasaryan
2023-09-27 5:25 ` [PATCH 3/6] mm: Handle shared faults " Matthew Wilcox (Oracle)
2023-09-28 0:46 ` Suren Baghdasaryan
2023-09-28 1:02 ` Suren Baghdasaryan
2023-09-28 5:33 ` Matthew Wilcox
2023-09-28 15:02 ` Suren Baghdasaryan
2023-09-27 5:25 ` [PATCH 4/6] mm: Handle COW " Matthew Wilcox (Oracle)
2023-09-28 0:53 ` Suren Baghdasaryan
2023-09-27 5:25 ` [PATCH 5/6] mm: Handle read " Matthew Wilcox (Oracle)
2023-09-27 5:25 ` [PATCH 6/6] mm: Handle write faults to RO pages " Matthew Wilcox (Oracle)
2023-09-27 22:18 ` Suren Baghdasaryan [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=CAJuCfpE69Cbt7AHL2iQuTU578hP5wi0soOVp6i67QE1SeCrAHQ@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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