From: Namhyung Kim <namhyung@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Ravi Bangoria <ravi.bangoria@amd.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] perf/core: Introduce cpuctx->cgrp_ctx_list
Date: Wed, 4 Oct 2023 14:27:46 -0700 [thread overview]
Message-ID: <ZR3Y0sqMJICfJuDF@google.com> (raw)
In-Reply-To: <ZR2H+WtRexpOffTw@gmail.com>
On Wed, Oct 04, 2023 at 05:42:49PM +0200, Ingo Molnar wrote:
>
> * Namhyung Kim <namhyung@kernel.org> wrote:
>
> > Maybe I can add an option to perf bench sched to place
> > senders and receivers in different cgroups.
>
> That would certainly be useful to measure cgroups overhead.
Sent out the change:
https://lore.kernel.org/all/20231004204741.985422-1-namhyung@kernel.org/
With that, the numbers became stable. :)
Before)
$ taskset -c 0 ./perf bench sched pipe -l 10000 -G AAA,BBB
# Running 'sched/pipe' benchmark:
# Executed 10000 pipe operations between two processes
Total time: 0.901 [sec]
90.128700 usecs/op
11095 ops/sec
After)
$ taskset -c 0 ./perf bench sched pipe -l 10000 -G AAA,BBB
# Running 'sched/pipe' benchmark:
# Executed 10000 pipe operations between two processes
Total time: 0.065 [sec]
6.560100 usecs/op
152436 ops/sec
Thanks,
Namhyung
next prev parent reply other threads:[~2023-10-04 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 4:08 [PATCH] perf/core: Introduce cpuctx->cgrp_ctx_list Namhyung Kim
2023-10-04 7:26 ` Ingo Molnar
2023-10-04 15:01 ` Namhyung Kim
2023-10-04 15:42 ` Ingo Molnar
2023-10-04 21:27 ` Namhyung Kim [this message]
2023-10-04 16:02 ` Peter Zijlstra
2023-10-04 16:32 ` Namhyung Kim
2023-10-09 21:04 ` Peter Zijlstra
2023-10-10 4:57 ` Namhyung Kim
2023-10-11 3:45 ` Namhyung Kim
2023-10-11 7:51 ` Peter Zijlstra
2023-10-11 9:50 ` Peter Zijlstra
2023-10-11 16:02 ` Namhyung Kim
2023-10-12 17:34 ` [tip: perf/core] perf: Optimize perf_cgroup_switch() tip-bot2 for Peter Zijlstra
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=ZR3Y0sqMJICfJuDF@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.