From: "David Wang" <00107082@163.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
namhyung@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: Wed, 15 Nov 2023 18:59:34 +0800 (CST) [thread overview]
Message-ID: <407a06f8.632a.18bd2a2ece1.Coremail.00107082@163.com> (raw)
In-Reply-To: <20231115103241.GD3818@noisy.programming.kicks-ass.net>
At 2023-11-15 18:32:41, "Peter Zijlstra" <peterz@infradead.org> wrote:
>
>Namhyung, could you please take a look, you know how to operate this
>cgroup stuff.
>
More information, I run the profiling with 8cpu machine on a SSD with ext4 filesystem :
# mkdir /sys/fs/cgroup/mytest
# echo $$ > /sys/fs/cgroup/mytest/cgroup.procs
## Start profiling targeting cgroup /sys/fs/cgroup/mytest on another terminal
# fio --randrepeat=1 --ioengine=libaio --direct=1 --name=test --bs=4k --iodepth=64 --size=1G --readwrite=randrw --runtime=600 --numjobs=4 --time_based=1
I got a feeling that f06cc667f7990 would decrease total samples by 10%~20% when profiling IO benchmark within cgroup.
David Wang
next prev parent reply other threads:[~2023-11-15 11:00 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 [this message]
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
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=407a06f8.632a.18bd2a2ece1.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).