From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Leo Yan <leo.yan@arm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tests: Don't retest sections in "Object code reading"
Date: Mon, 6 Oct 2025 17:03:20 -0300 [thread overview]
Message-ID: <aOQgiN0IlSso_L6d@x1> (raw)
In-Reply-To: <CAP-5=fXmAbz7Gp5eCRFYsYu_pZoFNSR+mcJgE6Eu6YewHyLNtg@mail.gmail.com>
On Mon, Oct 06, 2025 at 08:21:12AM -0700, Ian Rogers wrote:
> On Mon, Oct 6, 2025 at 6:11 AM James Clark <james.clark@linaro.org> wrote:
> > We already only test each kcore map once, but on slow systems
> > (particularly with network filesystems) even the non-kcore maps are
> > slow. The test can test the same objump output over and over which only
> > wastes time. Generalize the skipping mechanism to track all DSOs and
> > addresses so that each section is only tested once.
> >
> > On a fully loaded Arm Juno (simulating a parallel Perf test run) with a
> > network filesystem, the original runtime is:
> >
> > real 1m51.126s
> > user 0m19.445s
> > sys 1m15.431s
> >
> > And the new runtime is:
> >
> > real 0m48.873s
> > user 0m8.031s
> > sys 0m32.353s
> >
> > Signed-off-by: James Clark <james.clark@linaro.org>
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Thanks, applied to perf-tools-next,
- Arnaldo
next prev parent reply other threads:[~2025-10-06 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 13:11 [PATCH] perf tests: Don't retest sections in "Object code reading" James Clark
2025-10-06 15:21 ` Ian Rogers
2025-10-06 20:03 ` Arnaldo Carvalho de Melo [this message]
2025-10-07 9:10 ` James Clark
2025-10-07 13:16 ` Ian Rogers
2025-10-07 20:01 ` Arnaldo Carvalho de Melo
2025-10-08 8:32 ` James Clark
2025-10-08 10:21 ` James Clark
2025-10-08 13:39 ` Dan Carpenter
2025-10-08 14:11 ` James Clark
2025-10-08 15:07 ` Ian Rogers
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=aOQgiN0IlSso_L6d@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@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;
as well as URLs for NNTP newsgroup(s).