[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250716155545.ad2efdd41c85d6812bf328bb@linux-foundation.org>
Date: Wed, 16 Jul 2025 15:55:45 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: Liam.Howlett@...cle.com, lorenzo.stoakes@...cle.com, david@...hat.com,
vbabka@...e.cz, peterx@...hat.com, jannh@...gle.com, hannes@...xchg.org,
mhocko@...nel.org, paulmck@...nel.org, shuah@...nel.org,
adobriyan@...il.com, brauner@...nel.org, josef@...icpanda.com,
yebin10@...wei.com, linux@...ssschuh.net, willy@...radead.org,
osalvador@...e.de, andrii@...nel.org, ryan.roberts@....com,
christophe.leroy@...roup.eu, tjmercier@...gle.com, kaleshsingh@...gle.com,
aha310510@...il.com, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v7 0/7] use per-vma locks for /proc/pid/maps reads
On Tue, 15 Jul 2025 20:05:49 -0700 Suren Baghdasaryan <surenb@...gle.com> wrote:
> This patchset switches from holding mmap_lock while reading /proc/pid/maps
> to taking per-vma locks as we walk the vma tree.
Thanks, I added this v7 series to mm-new. Which I usually push out
mid-evening California time.
Powered by blists - more mailing lists