From: David Hildenbrand <david@kernel.org>
To: David Hildenbrand <david@kernel.org>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <liam@infradead.org>,
Nico Pache <nico.pache@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>,
Lance Yang <lance.yang@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
Kiryl Shutsemau <kas@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Jose A. Perez de Azpillaga" <azpijr@gmail.com>
Subject: Re: [PATCH v3 0/3] mm/khugepaged: bound mmap_lock hold time when walking an mm's VMAs
Date: Thu, 12 Nov 2026 10:39:33 +0100 [thread overview]
Message-ID: <179447637396.7058.8722598190835864744.b4-ty@b4> (raw)
In-Reply-To: <20261110-khugepaged-latency-fix-v3-0-6eea743cf9a3@kernel.org>
On Tue, 10 Nov 2026 17:19:10 +0000, Lorenzo Stoakes (ARM) wrote:
> This series introduces a couple small changes to khugepaged to improve its
> behaviour both in the face of mm->mmap_lock contention and to reduce that
> lock contention when possible.
>
> Looking at the first change - if the mmap lock is contended, an attempted
> mmap trylock in collapse_scan_mm_slot() will result in the scan being
> aborted wherever it happens to be, and when next the mm is processed it
> starts from the beginning again.
>
> [...]
Applied, thanks!
tree: mm/core.git
branch: thp-7.5.misc
Applied patches will appear soon in mm-next, followed by linux-next.
Please report any outstanding bugs that were missed during review, so we
can either drop the patch series or decide how to fix it up.
It is encouraged to provide Acked-bys, Reviewed-bys, and Tested-bys even
though the patches have already been applied. If possible, patch trailers
will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. Further, this is not a guarantee that the
patches will go upstream. If in doubt, please check the listed branch.
[1/3] Revert "mm/khugepaged: remove definition of struct khugepaged_mm_slot"
https://git.kernel.org/mm/core/c/3734f01d
[2/3] mm/khugepaged: scan mm's more efficiently under mmap_lock contention
https://git.kernel.org/mm/core/c/f4720f7b
[3/3] mm/khugepaged: release contended mmap read lock after scanning enough VMAs
https://git.kernel.org/mm/core/c/f616e41a
--
Cheers,
David
prev parent reply other threads:[~2026-11-12 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 17:19 Lorenzo Stoakes (ARM)
2026-11-10 17:19 ` [PATCH v3 1/3] Revert "mm/khugepaged: remove definition of struct khugepaged_mm_slot" Lorenzo Stoakes (ARM)
2026-11-10 17:19 ` [PATCH v3 2/3] mm/khugepaged: scan mm's more efficiently under mmap_lock contention Lorenzo Stoakes (ARM)
2026-11-10 17:19 ` [PATCH v3 3/3] mm/khugepaged: release contended mmap read lock after scanning enough VMAs Lorenzo Stoakes (ARM)
2026-11-10 19:09 ` Lorenzo Stoakes (ARM)
2026-11-12 9:26 ` David Hildenbrand (Arm)
2026-11-11 9:27 ` David Hildenbrand (Arm)
2026-11-11 9:30 ` Lorenzo Stoakes (ARM)
2026-11-12 9:39 ` David Hildenbrand [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=179447637396.7058.8722598190835864744.b4-ty@b4 \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=azpijr@gmail.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=usama.arif@linux.dev \
--cc=ziy@nvidia.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
all inboxes | Powered by JetHome®