From: sashiko-bot@kernel.org
To: "Max Kellermann" <max.kellermann@ionos.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf: skip unnecessary userspace map synthesis
Date: Tue, 13 Oct 2026 13:11:09 +0000 [thread overview]
Message-ID: <sashiko-outbox-169780@kernel.org> (raw)
In-Reply-To: <20261013130052.3012773-1-max.kellermann@ionos.com>
> Reading `/proc/PID/task/PID/maps` for existing processes is expensive
> on systems with many processes. `perf record` already allows skipping
> these reads with the `--synth=` option, but `perf top` has no
> equivalent option.
>
> Skip userspace map synthesis by default in `record` and `top` when all
> events exclude userspace and no sample feature needs user mappings.
>
> Signed-off-by: Max Kellermann <max.kellermann@ionos.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261013130052.3012773-1-max.kellermann@ionos.com?part=1
next prev parent reply other threads:[~2026-10-13 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:00 [PATCH] perf: skip unnecessary userspace map synthesis Max Kellermann
2026-10-13 13:11 ` sashiko-bot [this message]
2026-10-13 13:29 ` Ian Rogers
2026-10-13 14:22 ` Max Kellermann
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=sashiko-outbox-169780@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=sashiko-reviews@lists.linux.dev \
/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