Date: Wed 02 Sep 2026 04:30:30 PM PDT Test set: performance Kernel: 7.2.2-300.fc44.x86_64 Release: Fedora release 44 (Forty Four) Result: PASS Failed Tests: None Warned Tests: None ============================================================ Starting test ./secureboot/check_SB_signature pesign is required to check the secure boot signature Starting test ./performance/lmbench3 cd src && make make[1]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' gmake[2]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' gmake[2]: Nothing to be done for 'all'. gmake[2]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' gmake[2]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' gmake[2]: Nothing to be done for 'opt'. gmake[2]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' make[1]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' cd src && make results make[1]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' gmake[2]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' gmake[2]: Nothing to be done for 'all'. gmake[2]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' gmake[2]: Entering directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' gmake[2]: Nothing to be done for 'opt'. gmake[2]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' ===================================================================== L M B E N C H C ON F I G U R A T I O N ---------------------------------------- You need to configure some parameters to lmbench. Once you have configured these parameters, you may do multiple runs by saying "make rerun" in the src subdirectory. NOTICE: please do not have any other activity on the system if you can help it. Things like the second hand on your xclock or X perfmeters are not so good when benchmarking. In fact, X is not so good when benchmarking. ===================================================================== Hang on, we are calculating your timing granularity. OK, it looks like you can time stuff down to 5000 usec resolution. Hang on, we are calculating your timing overhead. OK, it looks like your gettimeofday() costs 0 usecs. Hang on, we are calculating your loop overhead. OK, it looks like your benchmark loop costs 0.00000000 usecs. ===================================================================== If you are running on an MP machine and you want to try running multiple copies of lmbench in parallel, you can specify how many here. Using this option will make the benchmark run 100x slower (sorry). NOTE: WARNING! This feature is experimental and many results are known to be incorrect or random! MULTIPLE COPIES [default 1] Options to control job placement 1) Allow scheduler to place jobs 2) Assign each benchmark process with any attendent child processes to its own processor 3) Assign each benchmark process with any attendent child processes to its own processor, except that it will be as far as possible from other processes 4) Assign each benchmark and attendent processes to their own processors 5) Assign each benchmark and attendent processes to their own processors, except that they will be as far as possible from each other and other processes 6) Custom placement: you assign each benchmark process with attendent child processes to processors 7) Custom placement: you assign each benchmark and attendent processes to processors Note: some benchmarks, such as bw_pipe, create attendent child processes for each benchmark process. For example, bw_pipe needs a second process to send data down the pipe to be read by the benchmark process. If you have three copies of the benchmark process running, then you actually have six processes; three attendent child processes sending data down the pipes and three benchmark processes reading data and doing the measurements. Job placement selection: ===================================================================== Several benchmarks operate on a range of memory. This memory should be sized such that it is at least 4 times as big as the external cache[s] on your system. It should be no more than 80% of your physical memory. The bigger the range, the more accurate the results, but larger sizes take somewhat longer to run the benchmark. MB [default 90087] Checking to see if you have 90087 MB; please wait for a moment... Hang on, we are calculating your cache line size. OK, it looks like your cache line is bytes. ===================================================================== lmbench measures a wide variety of system performance, and the full suite of benchmarks can take a long time on some platforms. Consequently, we offer the capability to run only predefined subsets of benchmarks, one for operating system specific benchmarks and one for hardware specific benchmarks. We also offer the option of running only selected benchmarks which is useful during operating system development. Please remember that if you intend to publish the results you either need to do a full run or one of the predefined OS or hardware subsets. SUBSET (ALL|HARWARE|OS|DEVELOPMENT) [default all] ===================================================================== This benchmark measures, by default, file system latency. That can take a long time on systems with old style file systems (i.e., UFS, FFS, etc.). Linux' ext2fs and Sun's tmpfs are fast enough that this test is not painful. If you are planning on sending in these results, please don't do a fast run. If you want to skip the file system latency tests, answer "yes" below. SLOWFS [default no] ===================================================================== If you are running on an idle network and there are other, identically configured systems, on the same wire (no gateway between you and them), and you have rsh access to them, then you should run the network part of the benchmarks to them. Please specify any such systems as a space separated list such as: ether-host fddi-host hippi-host. REMOTE [default none] ===================================================================== Calculating mhz, please wait for a moment... I think your CPU mhz is 5010 MHz, 0.1996 nanosec clock but I am frequently wrong. If that is the wrong Mhz, type in your best guess as to your processor speed. It doesn't have to be exact, but if you know it is around 800, say 800. Please note that some processors, such as the P4, have a core which is double-clocked, so on those processors the reported clock speed will be roughly double the advertised clock rate. For example, a 1.8GHz P4 may be reported as a 3592MHz processor. Processor mhz [default 5010 MHz, 0.1996 nanosec clock] ===================================================================== We need a place to store a 90087 Mbyte file as well as create and delete a large number of small files. We default to /usr/tmp. If /usr/tmp is a memory resident file system (i.e., tmpfs), pick a different place. Please specify a directory that has enough space and is a local file system. FSDIR [default /usr/tmp] ===================================================================== lmbench outputs status information as it runs various benchmarks. By default this output is sent to /dev/tty, but you may redirect it to any file you wish (such as /dev/null...). Status output file [default /dev/tty] ===================================================================== There is a database of benchmark results that is shipped with new releases of lmbench. Your results can be included in the database if you wish. The more results the better, especially if they include remote networking. If your results are interesting, i.e., for a new fast box, they may be made available on the lmbench web page, which is http://www.bitmover.com/lmbench Mail results [default yes] OK, no results mailed. ===================================================================== Confguration done, thanks. There is a mailing list for discussing lmbench hosted at BitMover. Send mail to majordomo@bitmover.com to join the list. make[1]: Leaving directory '/home/luya/Documents/fedora-scm/kernel-tests/performance/lmbench3/src' L M B E N C H 3 . 0 S U M M A R Y ------------------------------------ (Alpha software, do not distribute) Processor, Processes - times in microseconds - smaller is better ------------------------------------------------------------------------------ Host OS Mhz null null open slct sig sig fork exec sh call I/O stat clos TCP inst hndl proc proc proc --------- ------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- kwetu-tel Linux 6.3.1-2 4544 0.05 0.13 0.79 1.59 2.72 0.11 0.91 234. 995. 1397 kwetu-tel Linux 6.4.2-2 4544 0.05 0.13 0.71 1.39 2.70 0.10 0.80 203. 907. 1285 kwetu-tel Linux 7.1.2-2 4544 0.28 0.36 1.54 2.81 3.65 0.32 2.00 446. 2021 3071 kwetu-tel Linux 6.7.1-2 4544 0.13 0.22 1.68 3.10 4.29 0.19 1.43 321. 1458 2073 kwetu-tel Linux 6.9.1-2 4544 0.12 0.20 1.62 2.89 3.84 0.17 1.34 371. 1466 2103 kwetu-tel Linux 6.11.0- 4544 0.11 0.18 1.56 2.84 3.76 0.17 1.33 430. 1617 2317 kwetu-tel Linux 6.13.3- 4544 0.11 0.17 1.49 2.57 3.80 0.16 1.43 434. 1815 3617 kwetu-tel Linux 6.15.2- 4544 0.12 0.18 1.54 2.68 3.69 0.17 1.49 405. 1586 2518 kwetu-tel Linux 6.18.1- 4544 0.25 0.32 1.59 2.80 3.88 0.30 1.59 372. 1957 2800 kwetu-tel Linux 7.0.1-2 4544 0.26 0.35 1.47 2.76 3.63 0.31 1.58 490. 1977 2901 kwetu-tel Linux 7.0.2-2 4544 0.26 0.34 1.46 2.75 3.62 0.31 1.56 467. 2065 2817 kwetu.tel Linux 7.2.2-3 5010 0.27 0.34 1.41 2.67 3.49 0.30 1.52 395. 1785 2299 Context switching - times in microseconds - smaller is better ------------------------------------------------------------------------- Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw --------- ------------- ------ ------ ------ ------ ------ ------- ------- kwetu-tel Linux 6.3.1-2 2.1700 2.2000 2.1900 2.4500 2.4800 2.46000 2.62000 kwetu-tel Linux 6.4.2-2 2.0600 2.0600 2.1300 2.3900 2.4100 2.32000 2.54000 kwetu-tel Linux 7.1.2-2 2.8300 2.2700 2.0800 2.6800 2.8700 2.69000 3.41000 kwetu-tel Linux 6.7.1-2 3.3100 3.3100 3.3400 3.6000 3.6600 3.63000 3.88000 kwetu-tel Linux 6.9.1-2 2.5400 2.2000 2.5100 2.5500 2.7300 2.77000 2.92000 kwetu-tel Linux 6.11.0- 2.3000 2.4300 2.5500 2.7400 2.8200 2.50000 3.34000 kwetu-tel Linux 6.13.3- 2.6300 2.6700 2.6300 3.1200 3.7300 3.19000 3.79000 kwetu-tel Linux 6.15.2- 2.7500 2.7100 2.8800 3.4000 3.5400 3.66000 4.22000 kwetu-tel Linux 6.18.1- 2.1700 2.5300 1.9700 2.7300 3.0000 3.10000 3.42000 kwetu-tel Linux 7.0.1-2 2.1200 2.1900 2.0000 2.5900 3.2700 2.96000 3.46000 kwetu-tel Linux 7.0.2-2 2.1200 2.1900 2.0200 2.5600 2.9300 2.90000 3.11000 kwetu.tel Linux 7.2.2-3 1.9800 2.1500 2.4000 2.7800 2.7600 2.84000 3.30000 *Local* Communication latencies in microseconds - smaller is better --------------------------------------------------------------------- Host OS 2p/0K Pipe AF UDP RPC/ TCP RPC/ TCP ctxsw UNIX UDP TCP conn --------- ------------- ----- ----- ---- ----- ----- ----- ----- ---- kwetu-tel Linux 6.3.1-2 2.170 5.095 4.34 9.293 10.6 17. kwetu-tel Linux 6.4.2-2 2.060 4.771 3.47 8.506 9.521 15. kwetu-tel Linux 7.1.2-2 2.830 6.721 7.36 14.9 17.1 29. kwetu-tel Linux 6.7.1-2 3.310 8.156 7.33 14.4 16.5 30. kwetu-tel Linux 6.9.1-2 2.540 6.843 6.78 12.3 14.7 29. kwetu-tel Linux 6.11.0- 2.300 6.016 6.82 12.0 14.3 28. kwetu-tel Linux 6.13.3- 2.630 6.689 7.01 13.2 15.1 28. kwetu-tel Linux 6.15.2- 2.750 6.656 7.19 13.7 16.6 31. kwetu-tel Linux 6.18.1- 2.170 6.187 7.31 13.7 16.3 31. kwetu-tel Linux 7.0.1-2 2.120 6.256 6.75 13.6 16.1 34. kwetu-tel Linux 7.0.2-2 2.120 6.377 6.81 12.7 15.1 30. kwetu.tel Linux 7.2.2-3 1.980 6.185 6.66 11.7 13.9 28. File & VM system latencies in microseconds - smaller is better ------------------------------------------------------------------------------- Host OS 0K File 10K File Mmap Prot Page 100fd Create Delete Create Delete Latency Fault Fault selct --------- ------------- ------ ------ ------ ------ ------- ----- ------- ----- kwetu-tel Linux 6.3.1-2 8.9615 8.7785 13.0 10.2 1437.4K 0.202 0.656 kwetu-tel Linux 6.4.2-2 8.3798 7.4773 11.2 8.8995 1361.8K 0.210 0.667 kwetu-tel Linux 7.1.2-2 22.9 34.9 35.1 41.9 3454.4K 0.495 1.454 kwetu-tel Linux 6.7.1-2 17.1 18.3 24.9 22.7 2613.1K 0.378 1.248 kwetu-tel Linux 6.9.1-2 68.4 17.6 23.2 22.3 2570.7K 0.411 1.008 kwetu-tel Linux 6.11.0- 15.7 17.4 23.0 21.5 608.3K 0.280 0.998 kwetu-tel Linux 6.13.3- 16.2 18.6 24.6 21.3 588.2K 0.250 1.012 kwetu-tel Linux 6.15.2- 16.1 17.0 24.5 19.9 559.0K 0.234 0.952 kwetu-tel Linux 6.18.1- 18.6 17.0 25.5 20.2 2631.7K 0.412 1.147 kwetu-tel Linux 7.0.1-2 16.6 23.5 27.2 22.9 3749.7K 0.396 1.194 kwetu-tel Linux 7.0.2-2 21.0 17.3 25.3 21.2 2446.3K 0.400 1.190 kwetu.tel Linux 7.2.2-3 21.9 37.0 31.7 37.6 49.2M 0.395 1.147 *Local* Communication bandwidths in MB/s - bigger is better ----------------------------------------------------------------------------- Host OS Pipe AF TCP File Mmap Bcopy Bcopy Mem Mem UNIX reread reread (libc) (hand) read write --------- ------------- ---- ---- ---- ------ ------ ------ ------ ---- ----- kwetu-tel Linux 6.3.1-2 5717 13.K 10.K 16.3K 27.5K 22.0K 10.8K 22.K 7604. kwetu-tel Linux 6.4.2-2 5444 13.K 12.K 15.4K 25.8K 19.7K 10.2K 22.K 6850. kwetu-tel Linux 7.1.2-2 3950 11.K 6386 14.3K 25.6K 20.3K 10.3K 22.K 7208. kwetu-tel Linux 6.7.1-2 3861 9582 6450 14.2K 26.1K 22.1K 12.1K 22.K 7808. kwetu-tel Linux 6.9.1-2 4419 9821 7493 15.4K 28.1K 22.0K 11.9K 23.K 7358. kwetu-tel Linux 6.11.0- 4740 12.K 7761 14.6K 27.2K 21.3K 11.9K 23.K 7625. kwetu-tel Linux 6.13.3- 4170 11.K 6954 15.2K 25.9K 19.9K 10.5K 24.K 7034. kwetu-tel Linux 6.15.2- 4095 12.K 6348 15.1K 27.3K 21.4K 10.6K 23.K 7387. kwetu-tel Linux 6.18.1- 4765 13.K 9193 15.0K 27.0K 20.9K 10.3K 23.K 7108. kwetu-tel Linux 7.0.1-2 4246 12.K 5596 11.9K 18.8K 12.2K 7365.5 17.K 5084. kwetu-tel Linux 7.0.2-2 4231 12.K 7211 11.9K 19.8K 13.0K 7458.9 17.K 5351. kwetu.tel Linux 7.2.2-3 7290 8435 9755 15.4K 28.0K 20.5K 10.2K 23.K 7284.