From: "Prundeanu, Cristian" <cpru@amazon.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>,
"Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>,
"Saidi, Ali" <alisaidi@amazon.com>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Blake, Geoff" <blakgeof@amazon.com>,
"Csoma, Csaba" <csabac@amazon.com>,
"Doebel, Bjoern" <doebel@amazon.de>,
Gautham Shenoy <gautham.shenoy@amd.com>,
Swapnil Sapkal <swapnil.sapkal@amd.com>,
Joseph Salisbury <joseph.salisbury@oracle.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: EEVDF regression still exists
Date: Tue, 29 Apr 2025 22:06:40 +0000 [thread overview]
Message-ID: <82DC7187-7CED-4285-85FC-7181688CD873@amazon.com> (raw)
In-Reply-To: <20250429215604.GE4439@noisy.programming.kicks-ass.net>
On 2025-04-29, 16:57, "Peter Zijlstra" <peterz@infradead.org <mailto:peterz@infradead.org>> wrote:
>> Here are the latest results for the EEVDF impact on database workloads.
>> The regression introduced in kernel 6.6 still persists and doesn't look
>> like it is improving.
>
> Well, I was under the impression it had actually been solved :-(
>
> My understanding from the last round was that Prateek and co had it
> sorted -- with the caveat being that you had to stick SCHED_BATCH in at
> the right place in MySQL start scripts or somesuch.
The statement in the previous thread [1] was that using SCHED_BATCH improves
performance over default. While that still holds true, it is also equally true
about using SCHED_BATCH on kernel 6.5.
So, when we compare 6.5 with recent kernels, both using SCHED_BATCH, the
regression is still visible. (Previously, we only compared SCHED_BATCH with
6.5 default, leading to the wrong conclusion that it's a fix).
[1] https://lore.kernel.org/all/feb31b6e-6457-454c-a4f3-ce8ad96bf8de@amd.com/
next prev parent reply other threads:[~2025-04-29 22:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 21:38 EEVDF regression still exists Cristian Prundeanu
2025-04-29 21:56 ` Peter Zijlstra
2025-04-29 22:06 ` Prundeanu, Cristian [this message]
2025-04-30 3:33 ` K Prateek Nayak
2025-05-01 16:16 ` Prundeanu, Cristian
2025-05-02 5:56 ` K Prateek Nayak
2025-05-02 6:33 ` K Prateek Nayak
2025-05-02 18:06 ` Prundeanu, Cristian
2025-05-02 8:48 ` Peter Zijlstra
2025-05-02 16:52 ` Prundeanu, Cristian
2025-05-14 21:26 ` Dietmar Eggemann
2025-04-30 10:02 ` Peter Zijlstra
2025-05-02 7:08 ` Sapkal, Swapnil
2025-05-02 17:25 ` Prundeanu, Cristian
2025-05-02 17:52 ` Linus Torvalds
2025-05-03 3:34 ` K Prateek Nayak
2025-05-21 13:30 ` Cristian Prundeanu
-- strict thread matches above, loose matches on Subject: below --
2025-05-20 18:14 Cristian Prundeanu
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=82DC7187-7CED-4285-85FC-7181688CD873@amazon.com \
--to=cpru@amazon.com \
--cc=abuehaze@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=blakgeof@amazon.com \
--cc=bp@alien8.de \
--cc=csabac@amazon.com \
--cc=dietmar.eggemann@arm.com \
--cc=doebel@amazon.de \
--cc=gautham.shenoy@amd.com \
--cc=joseph.salisbury@oracle.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=swapnil.sapkal@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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