From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Suren Baghdasaryan <surenb@google.com>,
Peter Xu <peterx@redhat.com>
Subject: [PATCH 0/4] Improve anon_vma scalability for anon VMAs
Date: Fri, 26 Apr 2024 15:44:59 +0100 [thread overview]
Message-ID: <20240426144506.1290619-1-willy@infradead.org> (raw)
We have a 3x throughput improvement reported by Intel's kernel test
robot: https://lore.kernel.org/all/202404261055.c5e24608-oliver.sang@intel.com/
This is from delaying taking the mmap_lock for page faults until we
actually need the mmap_lock in order to assign an anon_vma to the vma.
It cleans up the page fault path a little by making the anon fault
handler more similar to the file fault handler.
Matthew Wilcox (Oracle) (4):
mm: Assert the mmap_lock is held in __anon_vma_prepare()
mm: Delay the check for a NULL anon_vma
mm: Fix some minor per-VMA lock issues in userfaultfd
mm: Optimise vmf_anon_prepare() for VMAs without an anon_vma
mm/huge_memory.c | 6 ++++--
mm/memory.c | 42 +++++++++++++++++++++++++++---------------
mm/rmap.c | 3 +--
mm/userfaultfd.c | 20 +++++++++-----------
4 files changed, 41 insertions(+), 30 deletions(-)
--
2.43.0
next reply other threads:[~2024-04-26 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 14:44 Matthew Wilcox (Oracle) [this message]
2024-04-26 14:45 ` [PATCH 1/4] mm: Assert the mmap_lock is held in __anon_vma_prepare() Matthew Wilcox (Oracle)
2024-04-26 15:23 ` Suren Baghdasaryan
2024-04-26 17:34 ` David Hildenbrand
2024-04-26 14:45 ` [PATCH 2/4] mm: Delay the check for a NULL anon_vma Matthew Wilcox (Oracle)
2024-04-26 14:45 ` [PATCH 3/4] mm: Fix some minor per-VMA lock issues in userfaultfd Matthew Wilcox (Oracle)
2024-04-26 15:23 ` Suren Baghdasaryan
2024-04-26 14:45 ` [PATCH 4/4] mm: Optimise vmf_anon_prepare() for VMAs without an anon_vma Matthew Wilcox (Oracle)
2024-04-26 17:36 ` David Hildenbrand
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=20240426144506.1290619-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=surenb@google.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 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).