From: kernel test rebot <yi1.lai@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Ravi Bangoria <ravi.bangoria@amd.com>,
linux-efi@vger.kernel.org, yi1.lai@intel.com
Subject: [ardb:efi-arm-memmap-dtprop] [efivarfs] eaa4abe54e: stress-ng.get.ops_per_sec 2915.8% improvement
Date: Thu, 27 Aug 2026 09:15:11 +0800 [thread overview]
Message-ID: <202608270836.4a9957c0-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 2915.8% improvement of stress-ng.get.ops_per_sec on:
commit: eaa4abe54eb5de1ee002aa2e4f88fc49156f2fdb ("efivarfs: Cache occupied and available space") https://git.kernel.org/cgit/linux/kernel/git/ardb/linux.git efi-arm-memmap-dtprop
testcase: stress-ng
config: x86_64-rhel-9.4
compiler: gcc-14
test machine: 256 threads 2 sockets Intel(R) Xeon(R) 6768P CPU @ 2.4GHz (Granite Rapids) with 64G memory
parameters:
nr_threads: 100%
testtime: 60s
test: get
cpufreq_governor: performance
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260827/202608270836.4a9957c0-lkp@intel.com
=========================================================================================
compiler/cpufreq_governor/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
gcc-14/performance/x86_64-rhel-9.4/100%/debian-13-x86_64-20250902.cgz/lkp-gnr-2sp4/get/stress-ng/60s
commit:
44e4ec1a80 ("efi: apple-properties: validate setup data header length")
eaa4abe54e ("efivarfs: Cache occupied and available space")
44e4ec1a802d2078 eaa4abe54eb5de1ee002aa2e4f8
---------------- ---------------------------
%stddev %change %stddev
\ | \
15418287 +2912.1% 4.644e+08 stress-ng.get.ops
256967 +2915.8% 7749645 stress-ng.get.ops_per_sec
554.00 ± 4% +11739.5% 65591 stress-ng.time.involuntary_context_switches
69114 ± 17% -52.8% 32593 ± 2% stress-ng.time.minor_page_faults
209.30 +12040.1% 25409 stress-ng.time.percent_of_cpu_this_job_got
120.05 +12557.5% 15195 stress-ng.time.system_time
6.51 +1095.1% 77.76 stress-ng.time.user_time
97296 -41.8% 56610 ± 14% stress-ng.time.voluntary_context_switches
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-27 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608270836.4a9957c0-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=ravi.bangoria@amd.com \
/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