From: Athira Rajeev <atrajeev@linux.ibm.com>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-s390@vger.kernel.org,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-perf-users@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
yangtiezhu@loongson.cn, agordeev@linux.ibm.com,
gor@linux.ibm.com, sumanthk@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PATCH] perf/bench: Fix perf bench syscall XXXX loop count
Date: Tue, 4 Mar 2025 19:44:39 +0530 [thread overview]
Message-ID: <69345A2D-EF10-4530-8C95-1E7BDC0B64F1@linux.ibm.com> (raw)
In-Reply-To: <20250304092349.2618082-1-tmricht@linux.ibm.com>
> On 4 Mar 2025, at 2:53 PM, Thomas Richter <tmricht@linux.ibm.com> wrote:
>
> Command 'perf bench syscall fork -l 100000' offers option
> -l to run for a specified number of iterations. However this
> option is not always observed. The number is silently limited to
> 10000 iterations as can be seen:
>
> Output before:
> # perf bench syscall fork -l 100000
> # Running 'syscall/fork' benchmark:
> # Executed 10,000 fork() calls
> Total time: 23.388 [sec]
>
> 2338.809800 usecs/op
> 427 ops/sec
> #
>
> When explicitly specified with option -l or --loops, also observe
> higher number of iterations:
>
> Output after:
> # perf bench syscall fork -l 100000
> # Running 'syscall/fork' benchmark:
> # Executed 100,000 fork() calls
> Total time: 716.982 [sec]
>
> 7169.829510 usecs/op
> 139 ops/sec
> #
>
Tested-by: Athira Rajeev <atrajeev@linux.ibm.com>
Thanks
Athira
> This patch fixes the issue for basic execve fork and getpgid.
>
> Fixes: ece7f7c0507c ("perf bench syscall: Add fork syscall benchmark")
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> Acked-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
> Cc: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
> tools/perf/bench/syscall.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/tools/perf/bench/syscall.c b/tools/perf/bench/syscall.c
> index ea4dfc07cbd6..e7dc216f717f 100644
> --- a/tools/perf/bench/syscall.c
> +++ b/tools/perf/bench/syscall.c
> @@ -22,8 +22,7 @@
> #define __NR_fork -1
> #endif
>
> -#define LOOPS_DEFAULT 10000000
> -static int loops = LOOPS_DEFAULT;
> +static int loops;
>
> static const struct option options[] = {
> OPT_INTEGER('l', "loop", &loops, "Specify number of loops"),
> @@ -80,6 +79,18 @@ static int bench_syscall_common(int argc, const char **argv, int syscall)
> const char *name = NULL;
> int i;
>
> + switch (syscall) {
> + case __NR_fork:
> + case __NR_execve:
> + /* Limit default loop to 10000 times to save time */
> + loops = 10000;
> + break;
> + default:
> + loops = 10000000;
> + break;
> + }
> +
> + /* Options -l and --loops override default above */
> argc = parse_options(argc, argv, options, bench_syscall_usage, 0);
>
> gettimeofday(&start, NULL);
> @@ -94,16 +105,9 @@ static int bench_syscall_common(int argc, const char **argv, int syscall)
> break;
> case __NR_fork:
> test_fork();
> - /* Only loop 10000 times to save time */
> - if (i == 10000)
> - loops = 10000;
> break;
> case __NR_execve:
> test_execve();
> - /* Only loop 10000 times to save time */
> - if (i == 10000)
> - loops = 10000;
> - break;
> default:
> break;
> }
> --
> 2.47.0
>
>
next prev parent reply other threads:[~2025-03-04 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 9:23 [PATCH] perf/bench: Fix perf bench syscall XXXX loop count Thomas Richter
2025-03-04 14:14 ` Athira Rajeev [this message]
2025-03-06 17:14 ` 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=69345A2D-EF10-4530-8C95-1E7BDC0B64F1@linux.ibm.com \
--to=atrajeev@linux.ibm.com \
--cc=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@linux.ibm.com \
--cc=yangtiezhu@loongson.cn \
/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