From: "Doug Smythies" <dsmythies@telus.net>
To: "'Peter Zijlstra'" <peterz@infradead.org>
Cc: "'K Prateek Nayak'" <kprateek.nayak@amd.com>, <mingo@kernel.org>,
<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
<dietmar.eggemann@arm.com>, <rostedt@goodmis.org>,
<bsegall@google.com>, <mgorman@suse.de>, <vschneid@redhat.com>,
<linux-kernel@vger.kernel.org>, <wangtao554@huawei.com>,
<quzicheng@huawei.com>, "Doug Smythies" <dsmythies@telus.net>
Subject: RE: [PATCH 0/4] sched: Various reweight_entity() fixes
Date: Tue, 10 Feb 2026 21:51:01 -0800 [thread overview]
Message-ID: <004e01dc9b1a$6808bb90$381a32b0$@telus.net> (raw)
In-Reply-To: <20260210181308.GO2995752@noisy.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 1898 bytes --]
On 2026.02.10 10:13 Peter Zijlstra wrote:
> On Tue, Feb 03, 2026 at 08:36:41AM -0800, Doug Smythies wrote:
>
>> Further to my email from the other day, where all was good [1],
>> I have continued to test, in particular the severe overload conditions
>> from [2].
>
>> Conditions:
>> Greater than 12,500 X (yes > /dev/null) tasks
>> But less than 15,000 X ( yes > /dev/null) tasks
>>
>> I have tested up to 20,000 X (yes > /dev/null) tasks
>> with previous kernels, including mainline 6.19-rc1.
>>
>> I would not disagree if you say my operating conditions
>> are ridiculous.
>
> They absolutely are; however!, people do crazy things so I doubt you are
> alone.
>
>> System:
>> Processor: Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz, 6 cores 12 CPUs.
>> CPU frequency scaling driver: intel_pstate; Governor powersave.
>
> Right, so I was too lazy to find a matching test machine, but instead
> used taskset to limit myself to 6 cores/12 threads and let it rip.
>
> # taskset -c -p 0-5,24-29 $$
> # for ((i=0; i<20000; i++)) do yes > /dev/null & done
>
> ... a *LONG* while later ...
>
> And I have reached 15k.
>
> ... this is *SLOW* ...
Thanks for trying it.
And yes it gets very slow. I should have warned readers.
With the first version of this patch set it took my computer 20 minutes
to spin out 18,000 tasks. A graph is attached.
Note that more typically I could not get to 18,000 tasks. I don't know a
predictable way to create the hang.
By the way, I had no issue with 80,000 tasks, if they contained some
regular sleep time. A graph is attached. The load average was 79,400.
> So I reached 20000 and figured what the heck and went for another 5k.
>
> Eventually I managed to reach 21160, and then boom.
>
> It is one of those pick_next_task_fair() NULL pointer derefs that are so
> very indicative of math overflow.
>
> I'll try and have a poke, if only this were a faster thing ;-)
[-- Attachment #2: pz-tasks.png --]
[-- Type: image/png, Size: 17326 bytes --]
[-- Attachment #3: tasks-80000.png --]
[-- Type: image/png, Size: 25273 bytes --]
next prev parent reply other threads:[~2026-02-11 5:51 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 9:34 [PATCH 0/4] sched: Various reweight_entity() fixes Peter Zijlstra
2026-01-30 9:34 ` [PATCH 1/4] sched/fair: Only set slice protection at pick time Peter Zijlstra
2026-01-30 15:52 ` Vincent Guittot
2026-01-30 9:34 ` [PATCH 2/4] sched/eevdf: Update se->vprot in reweight_entity() Peter Zijlstra
2026-01-30 16:20 ` Vincent Guittot
2026-01-30 9:34 ` [PATCH 3/4] sched/fair: Increase weight bits for avg_vruntime Peter Zijlstra
2026-01-30 9:34 ` [PATCH 4/4] sched/fair: Revert 6d71a9c61604 ("sched/fair: Fix EEVDF entity placement bug causing scheduling lag") Peter Zijlstra
2026-01-31 1:47 ` Zhang Qiao
2026-01-31 15:21 ` Peter Zijlstra
2026-02-02 9:12 ` Peter Zijlstra
2026-02-02 9:24 ` Peter Zijlstra
2026-02-02 11:23 ` Zhang Qiao
2026-02-01 17:13 ` [PATCH 0/4] sched: Various reweight_entity() fixes Doug Smythies
2026-02-03 6:45 ` K Prateek Nayak
2026-02-03 11:11 ` Peter Zijlstra
2026-02-03 12:19 ` K Prateek Nayak
2026-02-03 16:36 ` Doug Smythies
2026-02-10 18:13 ` Peter Zijlstra
2026-02-11 5:51 ` Doug Smythies [this message]
2026-02-04 10:15 ` K Prateek Nayak
2026-02-09 15:47 ` Peter Zijlstra
2026-02-09 16:52 ` K Prateek Nayak
2026-02-10 5:16 ` K Prateek Nayak
2026-02-10 10:29 ` Peter Zijlstra
2026-02-10 15:41 ` Doug Smythies
2026-02-10 18:09 ` K Prateek Nayak
2026-02-10 18:35 ` Peter Zijlstra
2026-02-10 20:04 ` K Prateek Nayak
2026-02-11 6:28 ` K Prateek Nayak
2026-02-11 8:50 ` K Prateek Nayak
2026-02-11 23:09 ` Doug Smythies
2026-02-10 18:52 ` Peter Zijlstra
2026-02-10 20:52 ` Vincent Guittot
2026-02-11 5:21 ` Doug Smythies
2026-02-11 8:49 ` Vincent Guittot
2026-02-11 9:01 ` Peter Zijlstra
2026-02-11 10:48 ` Peter Zijlstra
2026-02-11 10:49 ` Peter Zijlstra
2026-02-11 11:15 ` Vincent Guittot
2026-02-11 16:28 ` Peter Zijlstra
2026-02-12 7:43 ` K Prateek Nayak
2026-02-12 11:59 ` Peter Zijlstra
2026-02-12 17:16 ` Peter Zijlstra
2026-02-12 17:24 ` Vincent Guittot
2026-02-12 19:31 ` Peter Zijlstra
2026-02-13 5:22 ` K Prateek Nayak
2026-02-13 6:44 ` Peter Zijlstra
2026-02-13 10:50 ` Peter Zijlstra
2026-02-13 14:29 ` K Prateek Nayak
2026-02-14 6:31 ` Doug Smythies
2026-02-21 22:51 ` Doug Smythies
2026-02-12 19:29 ` Peter Zijlstra
2026-02-12 19:37 ` Doug Smythies
2026-02-13 6:04 ` K Prateek Nayak
2026-02-11 16:21 ` Peter Zijlstra
2026-02-12 5:54 ` Doug Smythies
2026-02-12 7:51 ` Peter Zijlstra
2026-02-12 15:47 ` Doug Smythies
2026-02-12 7:46 ` Peter Zijlstra
2026-02-11 23:25 ` Doug Smythies
2026-02-11 8:48 ` Peter Zijlstra
2026-02-04 10:44 ` Peter Zijlstra
2026-02-14 7:20 ` Shubhang Kaushik
2026-02-16 3:14 ` K Prateek Nayak
2026-02-16 10:59 ` Dietmar Eggemann
2026-02-17 14:37 ` Dietmar Eggemann
2026-02-17 22:02 ` Shubhang Kaushik
2026-02-17 4:20 ` K Prateek Nayak
2026-02-18 18:37 ` Shubhang Kaushik
2026-02-19 7:53 ` Peter Zijlstra
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='004e01dc9b1a$6808bb90$381a32b0$@telus.net' \
--to=dsmythies@telus.net \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=quzicheng@huawei.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangtao554@huawei.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