From: "David Wang" <00107082@163.com>
To: "Namhyung Kim" <namhyung@kernel.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Regression or Fix]perf: profiling stats sigificantly changed for aio_write/read(ext4) between 6.7.0-rc1 and 6.6.0
Date: Thu, 16 Nov 2023 00:24:32 +0800 (CST) [thread overview]
Message-ID: <15854406.6b75.18bd3cc70a9.Coremail.00107082@163.com> (raw)
In-Reply-To: <CAM9d7cjY_NzPZKtQbSUzhLwrH+zAPB701PAiCHSmnvjcHnhLTQ@mail.gmail.com>
At 2023-11-15 23:45:38, "Namhyung Kim" <namhyung@kernel.org> wrote:
>Hello,
>
>>
>> On Tue, Nov 14, 2023 at 11:20:32PM +0800, David Wang wrote:
>> >
>> >
>> > At 2023-11-14 12:31:12, "David Wang" <00107082@163.com> wrote:
>> > >Hi,
>> > >
>> > >I was making kernel profiling to identify kernel changes between revisions under the load of fio benchmark,
>> >
>> > >But I did not notice a significant change in the overhead of perf tracing based on the fio report,
>> > >that is why I am not sure whether this is a regression or an improvement....
>> > >Just report the change.
>
>Do you mean f06cc667f79 ("perf: Optimize perf_cgroup_switch")?
Yes
>Did you have cgroup events when you ran the benchmark?
>Otherwise it should not make any differences.
>
My test happened to trigger frequent context switch (IO bench), and my profiling was targeting a cgroup (v2) where fio runs. , yes, cgroup and context switch :)
>
>> > I think there are some cases where pmu_ctx->nr_cgroups is zero but there is still cgroup event within, and some samples are missed, causing the stats changes, just a guess.
>
>I don't know what makes you think so. Do you see
>differences in the perf output? Any cgroup events having
>smaller number of samples or counts?
I obverse total sample count decreased 10%~20%, one report show sample count increase from 266521 to 317649 after reverting the commit.
But I did not use perf-tool, I will try it.
>
>Or was the fio benchmark degraded seriously?
>
Noop, benchmark did degrade when profiling is running, but no significant changes observed w/o the commit.
David Wang
prev parent reply other threads:[~2023-11-15 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 4:31 [Regression or Fix]perf: profiling stats sigificantly changed for aio_write/read(ext4) between 6.7.0-rc1 and 6.6.0 David Wang
2023-11-14 15:20 ` David Wang
2023-11-15 10:32 ` [Regression " Peter Zijlstra
2023-11-15 10:59 ` David Wang
2023-11-15 15:48 ` Namhyung Kim
2023-11-15 16:11 ` David Wang
2023-11-15 16:26 ` Namhyung Kim
2023-11-16 4:08 ` David Wang
2023-11-17 21:11 ` Namhyung Kim
2023-11-18 1:46 ` David Wang
2023-11-20 22:59 ` Namhyung Kim
2023-11-21 5:51 ` David Wang
2023-11-15 15:45 ` Namhyung Kim
2023-11-15 16:24 ` David Wang [this message]
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=15854406.6b75.18bd3cc70a9.Coremail.00107082@163.com \
--to=00107082@163.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--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).