All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <yi1.lai@intel.com>
To: Shubhang Kaushik <sh@gentwo.org>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Zhan Xusheng <zhanxusheng@xiaomi.com>,
	sched-ext@lists.linux.dev, aubrey.li@linux.intel.com,
	yu.c.chen@intel.com, yi1.lai@intel.com
Subject: [linus:master] [sched]  c72945693b: stress-ng.rawudp.packets_32_bytes_received_per_sec 34.2% improvement
Date: Tue, 27 Oct 2026 18:50:06 +0800	[thread overview]
Message-ID: <202610271134.d6bf1e10-lkp@intel.com> (raw)



Hello,

kernel test robot noticed a 34.2% improvement of stress-ng.rawudp.packets_32_bytes_received_per_sec on:


commit: c72945693b90423f1b46ac2dbc8749c2b7804fc8 ("sched: Restart fair hrtick after same-task repicks") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

testcase: stress-ng
config: x86_64-rhel-9.4
compiler: gcc-14
test machine: 192 threads 2 sockets Intel(R) Xeon(R) 6740E  CPU @ 2.4GHz (Sierra Forest) with 256G memory
parameters:

	nr_threads: 100%
	testtime: 60s
	test: rawudp
	cpufreq_governor: performance


Details are as below:
-------------------------------------------------------------------------------------------------->


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261027/202610271134.d6bf1e10-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-srf-2sp3/rawudp/stress-ng/60s

commit: 
  a9b3c75705 ("sched/headers: Replace __ASSEMBLY__ with __ASSEMBLER__ in the <uapi/linux/sched.h> header")
  c72945693b ("sched: Restart fair hrtick after same-task repicks")

a9b3c7570564de40 c72945693b90423f1b46ac2dbc8
---------------- --------------------------- 
         %stddev     %change         %stddev
             \          |                \  
      0.01          +100.0%       0.02        stress-ng.rawudp.MB_recv'd_per_sec
   4559098           +34.1%    6112029 ±  3%  stress-ng.rawudp.ops
     76041           +34.0%     101916 ±  3%  stress-ng.rawudp.ops_per_sec
    395.33           +34.2%     530.63 ±  3%  stress-ng.rawudp.packets_32_bytes_received_per_sec
   2611008 ±  2%     +14.9%    2999104 ±  5%  stress-ng.time.involuntary_context_switches
     47.70 ±  7%     +46.7%      69.96 ±  8%  stress-ng.time.user_time
  20919233 ±  4%     +41.7%   29638128 ±  2%  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-10-27 10:50 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=202610271134.d6bf1e10-lkp@intel.com \
    --to=yi1.lai@intel.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=sched-ext@lists.linux.dev \
    --cc=sh@gentwo.org \
    --cc=yu.c.chen@intel.com \
    --cc=zhanxusheng@xiaomi.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 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.