From: Andrew Morton <akpm@linux-foundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
liam@infradead.org, ljs@kernel.org, vbabka@kernel.org,
willy@infradead.org, jannh@google.com, paulmck@kernel.org,
pfalcato@suse.de, shuah@kernel.org, hsukrut3@gmail.com,
richard.weiyang@gmail.com, reddybalavignesh9979@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 0/3] use vma locks for proc/pid/{smaps|numa_maps} reads
Date: Tue, 26 May 2026 18:49:44 -0700 [thread overview]
Message-ID: <20260526184944.18c28d6980fd29ff12fbbe22@linux-foundation.org> (raw)
In-Reply-To: <CAJuCfpHPs54_hc_U9DCxtv=xikKHJMtqCEDN_4Y5aDqKhoBDnA@mail.gmail.com>
On Thu, 21 May 2026 08:16:01 -0700 Suren Baghdasaryan <surenb@google.com> wrote:
> > > It might be but the point of this patchset (and the previous one that
> > > made a similar change for /proc/pid/maps) is to reduce mmap_lock
> > > contention, not to speed up the read operation, which is not a
> > > performance critical part.
> >
> > Well, this interface has been around .. forever, so if there is a noticeable
> > change in performance it should be called out.
>
> Sorry, I missed your reply. I'll see if I can adopt Paul's test for
> /proc/pid/maps [1] for benchmarking smaps but I would expect similar
> results as was reported in [2].
How's it coming along ;)
> [1] https://github.com/paulmckrcu/proc-mmap_sem-test
> [2] https://lore.kernel.org/all/20250719182854.3166724-1-surenb@google.com/
I've moved this series to the tail of mm-unstable to permit more time.
next prev parent reply other threads:[~2026-05-27 1:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 6:27 [PATCH v2 0/3] use vma locks for proc/pid/{smaps|numa_maps} reads Suren Baghdasaryan
2026-04-26 6:27 ` [PATCH v2 1/3] fs/proc/task_mmu: read proc/pid/{smaps|numa_maps} under per-vma lock Suren Baghdasaryan
2026-05-28 15:17 ` Lorenzo Stoakes
2026-06-03 23:49 ` Suren Baghdasaryan
2026-06-04 7:14 ` Lorenzo Stoakes
2026-06-04 19:26 ` Suren Baghdasaryan
2026-06-04 19:52 ` Lorenzo Stoakes
2026-04-26 6:27 ` [PATCH v2 2/3] selftests/proc: ensure the test is performed at the right page boundary Suren Baghdasaryan
2026-04-26 6:27 ` [PATCH v2 3/3] selftests/proc: add /proc/pid/smaps tearing tests Suren Baghdasaryan
2026-04-26 19:59 ` [PATCH v2 0/3] use vma locks for proc/pid/{smaps|numa_maps} reads Andrew Morton
2026-05-13 3:50 ` Suren Baghdasaryan
2026-05-12 9:28 ` David Hildenbrand (Arm)
2026-05-13 3:58 ` Suren Baghdasaryan
2026-05-13 7:39 ` David Hildenbrand (Arm)
2026-05-21 15:16 ` Suren Baghdasaryan
2026-05-27 1:49 ` Andrew Morton [this message]
2026-05-28 15:37 ` Lorenzo Stoakes
2026-06-03 23:57 ` Suren Baghdasaryan
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=20260526184944.18c28d6980fd29ff12fbbe22@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hsukrut3@gmail.com \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=paulmck@kernel.org \
--cc=pfalcato@suse.de \
--cc=reddybalavignesh9979@gmail.com \
--cc=richard.weiyang@gmail.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
/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