From: Oliver Sang <oliver.sang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Fernand Sieber <sieberf@amazon.com>, <oe-lkp@lists.linux.dev>,
<lkp@intel.com>, <linux-kernel@vger.kernel.org>,
<aubrey.li@linux.intel.com>, <yu.c.chen@intel.com>,
Ingo Molnar <mingo@kernel.org>, <oliver.sang@intel.com>
Subject: Re: [linus:master] [sched/fair] 79104becf4: stress-ng.resched.ops_per_sec 44.6% regression
Date: Tue, 16 Dec 2025 10:42:27 +0800 [thread overview]
Message-ID: <aUDHE/SYbnKNVHMU@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20251212101244.GN3911114@noisy.programming.kicks-ass.net>
hi, Peter Zijlstra,
On Fri, Dec 12, 2025 at 11:12:44AM +0100, Peter Zijlstra wrote:
> On Thu, Dec 11, 2025 at 10:21:15PM +0800, kernel test robot wrote:
> >
> >
> > Hello,
> >
> > kernel test robot noticed a 44.6% regression of stress-ng.resched.ops_per_sec on:
> >
> >
> > commit: 79104becf42baeeb4a3f2b106f954b9fc7c10a3c ("sched/fair: Forfeit vruntime on yield")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> After nearly 2 decades of telling people that using yield() is UB
> (except in the Real-Time cases where it is well defined), I'm >.< close
> to not caring about this.
>
> IIRC this benchmark is literally something like running yield() in a
> loop, so boohoo. I'll look when there's a real workload that has a
> problem.
got it. we won't report performance impact of this commit from micro benchmark
tests again.
>
> > [still regression on linus/master cfd4039213e7b5a828c5b78e1b5235cac91af53d]
> > [still regression on linux-next/master 82bcd04d124a4d84580ea4a8ba6b120db5f512e7]
>
> What's with the still? AFAIK this is the first report of this.
our report is based on bisect results. for mainline report, we do a further
check upon latest linus/master and linux-next/master. we only report when the
regression still exists there. so above 2 lines is just for information.
prev parent reply other threads:[~2025-12-16 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 14:21 kernel test robot
2025-12-12 10:12 ` Peter Zijlstra
2025-12-16 2:42 ` Oliver Sang [this message]
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=aUDHE/SYbnKNVHMU@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=sieberf@amazon.com \
--cc=yu.c.chen@intel.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
all inboxes | Powered by JetHome®