netdev - Re: [herbert-cryptodev-2.6:master] [rhashtable] e1d3422c95: stress-ng.syscall.ops_per

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250103-singing-crow-of-fantasy-fd061f@leitao>
Date: Fri, 3 Jan 2025 05:41:56 -0800
From: Breno Leitao <leitao@...ian.org>
To: kernel test robot <oliver.sang@...el.com>, lkp@...el.com,
	oe-lkp@...ts.linux.dev
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-crypto@...r.kernel.org,
	Herbert Xu <herbert@...dor.apana.org.au>, Tejun Heo <tj@...nel.org>,
	netdev@...r.kernel.org
Subject: Re: [herbert-cryptodev-2.6:master] [rhashtable]  e1d3422c95:
 stress-ng.syscall.ops_per_sec 98.9% regression

Hello "kernel robot" team,

First of all, thank you very much for running these tests against the
linux kernel.

I am trying to reproduce this report, and I would appreciate some help
to understand what is being measured, and try to reproduce the reported
problem.

On Fri, Dec 27, 2024 at 11:10:11AM +0800, kernel test robot wrote:
> kernel test robot noticed a 98.9% regression of stress-ng.syscall.ops_per_sec on:

Is this metric coming from `bogo ops/s` from stress-ng?

I am trying to reproduce this problem, running the following script:
https://download.01.org/0day-ci/archive/20241227/202412271017.cad7675-lkp@intel.com/repro-script

And I see the output like the one below, but, it is unclear to me what
metric regressed stress-ng.syscall.ops_per_sec means exactly.  Would you
mind helping me to understand what is stress-ng.syscall.ops_per_sec and
how it maps to stress-ng metrics?

Output of `stress-ng --timeout 60 --times --verify --metrics --no-rand-seed --syscall 224`:

	stress-ng: info:  [59621] setting to a 1 min, 0 secs run per stressor
	stress-ng: info:  [59621] dispatching hogs: 224 syscall
	stress-ng: info:  [59647] syscall: using method 'fast75'
	stress-ng: info:  [59647] syscall: 292 system call tests, 219 (75.0%) fastest non-failing tests fully exercised
	stress-ng: info:  [59647] syscall: Top 10 fastest system calls (timings in nanosecs):
	stress-ng: info:  [59647] syscall:               System Call   Avg (ns)   Min (ns)   Max (ns)
	stress-ng: info:  [59647] syscall:                  pkey_get      156.0        127        185
	stress-ng: info:  [59647] syscall:                      time      212.5        195        230
	stress-ng: info:  [59647] syscall:                  pkey_set      235.5        193        278
	stress-ng: info:  [59647] syscall:              gettimeofday      282.5        255        310
	stress-ng: info:  [59647] syscall:                    getcpu      457.0        388        526
	stress-ng: info:  [59647] syscall:           set_robust_list      791.5        745        838
	stress-ng: info:  [59647] syscall:                    getgid     1137.0        974       1300
	stress-ng: info:  [59647] syscall:                 setresuid     1146.0       1070       1222
	stress-ng: info:  [59647] syscall:                    getuid     1162.5        902       1423
	stress-ng: info:  [59647] syscall:                 setresgid     1211.5       1159       1264
	stress-ng: metrc: [59621] stressor       bogo ops real time  usr time  sys time   bogo ops/s     bogo ops/s CPU used per       RSS Max
	stress-ng: metrc: [59621]                           (secs)    (secs)    (secs)   (real time) (usr+sys time) instance (%)          (KB)
	stress-ng: metrc: [59621] syscall          114464     86.78      1.27    364.05      1318.95         313.33         1.88          4500
	stress-ng: info:  [59621] for a 98.30s run time:
	stress-ng: info:  [59621]    3538.93s available CPU time
	stress-ng: info:  [59621]       1.26s user time   (  0.04%)
	stress-ng: info:  [59621]     366.66s system time ( 10.36%)
	stress-ng: info:  [59621]     367.92s total time  ( 10.40%)
	stress-ng: info:  [59621] load average: 80.45 43.94 20.82
	stress-ng: info:  [59621] skipped: 0
	stress-ng: info:  [59621] passed: 224: syscall (224)
	stress-ng: info:  [59621] failed: 0
	stress-ng: info:  [59621] metrics untrustworthy: 0
	stress-ng: info:  [59621] successful run completed in 1 min, 38.30 secs

Thank you!
--breno