From: sashiko-bot@kernel.org
To: "Hongru Zhang" <zhanghongru06@gmail.com>
Cc: linux-s390@vger.kernel.org,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH v6] mm: retry page faults once under the per-VMA lock
Date: Fri, 11 Sep 2026 03:07:54 +0000 [thread overview]
Message-ID: <20260911030755.0C0EB1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260911025613.1220845-1-zhanghongru@xiaomi.com>
> From: Hongru Zhang <zhanghongru@xiaomi.com>
>
> The per-VMA lock fault path releases the per-VMA lock when the folio
> cannot be locked. It then waits for the folio to become lockable
> without holding the VMA lock and retries the page fault. However,
> the retry always takes the mmap_lock instead of the per-VMA lock.
> This can cause serious lock contention when a writer is holding the
> mmap_lock at the same time.
>
> Add a single retry under the per-VMA lock in the architecture fault
> handler. This does not touch any page fault code in mm. The retry is
> very likely to succeed because the first page fault has already waited
> for the folio to become lockable. For example, this usually means that
> any required I/O has completed. This allows faults that can make
> progress on an immediate retry to stay on the per-VMA lock path,
> [ ... ]
>
> [1] https://gist.github.com/zhr250/c36c2c54d9351df37e12fd072d4926ef
> [2] https://gist.github.com/zhr250/218ffe693f842346b56434483127422c
>
> Signed-off-by: Hongru Zhang <zhanghongru@xiaomi.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260911025613.1220845-1-zhanghongru@xiaomi.com?part=1
prev parent reply other threads:[~2026-09-11 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 2:56 [PATCH v6] mm: retry page faults once under the per-VMA lock Hongru Zhang
2026-09-11 2:56 ` Hongru Zhang
2026-09-11 3:07 ` sashiko-bot [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=20260911030755.0C0EB1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=zhanghongru06@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.