From: Ingo Molnar <mingo@kernel.org>
To: Dirk Gouders <dirk@gouders.net>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf bench sched pipe: fix enforced blocking reads in worker_thread
Date: Sun, 23 Mar 2025 20:02:15 +0100 [thread overview]
Message-ID: <Z-Bat1oBCQqT5mt5@gmail.com> (raw)
In-Reply-To: <20250323140316.19027-2-dirk@gouders.net>
* Dirk Gouders <dirk@gouders.net> wrote:
> The function worker_thread() is programmed in a way that roughly
> doubles the number of expectable context switches, because it enforces
> blocking reads:
>
> Performance counter stats for 'perf bench sched pipe':
>
> 2,000,004 context-switches
>
> 11.859548321 seconds time elapsed
>
> 0.674871000 seconds user
> 8.076890000 seconds sys
>
> The result of this behavior is that the blocking reads by far dominate
> the performance analysis of 'perf bench sched pipe':
>
> Samples: 78K of event 'cycles:P', Event count (approx.): 27964965844
> Overhead Command Shared Object Symbol
> 25.28% sched-pipe [kernel.kallsyms] [k] read_hpet
> 8.11% sched-pipe [kernel.kallsyms] [k] retbleed_untrain_ret
> 2.82% sched-pipe [kernel.kallsyms] [k] pipe_write
>
> From the code, it is unclear if that behavior is wanted but the log
> says that at least Ingo Molnar aims to mimic lmbench's lat_ctx, that
> doesn't handle the pipe ends that way
> (https://sourceforge.net/p/lmbench/code/HEAD/tree/trunk/lmbench2/src/lat_ctx.c)
>
> Fix worker_thread() by always first feeding the write ends of the pipes
> and then trying to read.
>
> This roughly halves the context switches and runtime of pure
> 'perf bench sched pipe':
>
> Performance counter stats for 'perf bench sched pipe':
>
> 1,005,770 context-switches
>
> 6.033448041 seconds time elapsed
>
> 0.423142000 seconds user
> 4.519829000 seconds sys
>
> And the blocking reads do no longer dominate the analysis at the above
> extreme:
>
> Samples: 40K of event 'cycles:P', Event count (approx.): 14309364879
> Overhead Command Shared Object Symbol
> 12.20% sched-pipe [kernel.kallsyms] [k] read_hpet
> 9.23% sched-pipe [kernel.kallsyms] [k] retbleed_untrain_ret
> 3.68% sched-pipe [kernel.kallsyms] [k] pipe_write
>
> Signed-off-by: Dirk Gouders <dirk@gouders.net>
> ---
> tools/perf/bench/sched-pipe.c | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
>
> diff --git a/tools/perf/bench/sched-pipe.c b/tools/perf/bench/sched-pipe.c
> index e2562677df96..70139036d68f 100644
> --- a/tools/perf/bench/sched-pipe.c
> +++ b/tools/perf/bench/sched-pipe.c
> @@ -204,17 +204,10 @@ static void *worker_thread(void *__tdata)
> }
>
> for (i = 0; i < loops; i++) {
> - if (!td->nr) {
> - ret = read_pipe(td);
> - BUG_ON(ret != sizeof(int));
> - ret = write(td->pipe_write, &m, sizeof(int));
> - BUG_ON(ret != sizeof(int));
> - } else {
> - ret = write(td->pipe_write, &m, sizeof(int));
> - BUG_ON(ret != sizeof(int));
> - ret = read_pipe(td);
> - BUG_ON(ret != sizeof(int));
> - }
> + ret = write(td->pipe_write, &m, sizeof(int));
> + BUG_ON(ret != sizeof(int));
> + ret = read_pipe(td);
> + BUG_ON(ret != sizeof(int));
Yeah, this was unintended:
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
next prev parent reply other threads:[~2025-03-23 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 14:01 [PATCH] perf bench sched pipe: fix enforced blocking reads in worker_thread Dirk Gouders
2025-03-23 19:02 ` Ingo Molnar [this message]
2025-03-24 16:34 ` Namhyung Kim
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=Z-Bat1oBCQqT5mt5@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=dirk@gouders.net \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.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 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.