[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aSfO7fA-04SBtTug@casper.infradead.org>
Date: Thu, 27 Nov 2025 04:09:17 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Barry Song <21cnbao@...il.com>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org,
Barry Song <v-songbaohua@...o.com>,
Russell King <linux@...linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, Huacai Chen <chenhuacai@...nel.org>,
WANG Xuerui <kernel@...0n.name>,
Madhavan Srinivasan <maddy@...ux.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Paul Walmsley <pjw@...nel.org>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Gerald Schaefer <gerald.schaefer@...ux.ibm.com>,
Heiko Carstens <hca@...ux.ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ux.ibm.com>,
Sven Schnelle <svens@...ux.ibm.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, "H . Peter Anvin" <hpa@...or.com>,
David Hildenbrand <david@...nel.org>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
"Liam R . Howlett" <Liam.Howlett@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>, Mike Rapoport <rppt@...nel.org>,
Suren Baghdasaryan <surenb@...gle.com>,
Michal Hocko <mhocko@...e.com>, Pedro Falcato <pfalcato@...e.de>,
Jarkko Sakkinen <jarkko@...nel.org>,
Oscar Salvador <osalvador@...e.de>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Oven Liyang <liyangouwen1@...o.com>,
Mark Rutland <mark.rutland@....com>,
Ada Couprie Diaz <ada.coupriediaz@....com>,
Robin Murphy <robin.murphy@....com>,
Kristina Martšenko <kristina.martsenko@....com>,
Kevin Brodsky <kevin.brodsky@....com>,
Yeoreum Yun <yeoreum.yun@....com>,
Wentao Guan <guanwentao@...ontech.com>,
Thorsten Blum <thorsten.blum@...ux.dev>,
Steven Rostedt <rostedt@...dmis.org>,
Yunhui Cui <cuiyunhui@...edance.com>,
Nam Cao <namcao@...utronix.de>, Chris Li <chrisl@...nel.org>,
Kairui Song <kasong@...cent.com>,
Kemeng Shi <shikemeng@...weicloud.com>,
Nhat Pham <nphamcs@...il.com>, Baoquan He <bhe@...hat.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
loongarch@...ts.linux.dev, linuxppc-dev@...ts.ozlabs.org,
linux-riscv@...ts.infradead.org, linux-s390@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] mm: continue using per-VMA lock when retrying
page faults after I/O
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.
Powered by blists - more mailing lists