Thread (17 messages) 17 messages, 7 authors, 2026-04-04

Re: [RFC PATCH 0/2] mm: continue using per-VMA lock when retrying page faults after I/O

From: Matthew Wilcox <willy@infradead.org>
Date: 2025-11-27 04:10:17
Also in: linux-fsdevel, linux-mm, linux-riscv, linux-s390, lkml, loongarch

On Thu, Nov 27, 2025 at 09:14:36AM +0800, Barry Song wrote:
There is no need to always fall back to mmap_lock if the per-VMA
lock was released only to wait for pagecache or swapcache to
become ready.
Something I've been wondering about is removing all the "drop the MM
locks while we wait for I/O" gunk.  It's a nice amount of code removed:

 include/linux/pagemap.h |  8 +---
 mm/filemap.c            | 98 ++++++++++++-------------------------------------
 mm/internal.h           | 21 -----------
 mm/memory.c             | 13 +------
 mm/shmem.c              |  6 ---
 5 files changed, 27 insertions(+), 119 deletions(-)

and I'm not sure we still need to do it with per-VMA locks.  What I
have here doesn't boot and I ran out of time to debug it.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help