From: Mike Galbraith <efault@gmx.de>
To: Chengfeng Lin <lin2530632123@gmail.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/7] sched/eevdf: Move to a single runqueue
Date: Tue, 03 Nov 2026 06:28:58 +0100 [thread overview]
Message-ID: <41ac0a8e95e22870efe308e8df9921960c53d4bc.camel@gmx.de> (raw)
In-Reply-To: <CANGjgdnS2ZbyvxyeqsYeD_aAH3PYVaQHXfY_A661GeSUwxK4VQ@mail.gmail.com>
On Mon, 2026-11-02 at 15:58 +0800, Chengfeng Lin wrote:
>
> If you make further changes in this area, I'd be happy to rerun the
> context-switch benchmark across the full range of worker counts and
> share the results.
I'm sure this little regression will get fixed up as the dust settles.
My role was the easy one, that of hound.. all you need is spare cycles.
The good news from hunting excursion is that what the reporter's probe
did was to validate the DELAY_DEQUEUE mechanism as being a genuine QOS
improvement. The reported QOS regression was per measurement the
DELAY_DEQUEUE progression going missing when all cycles expended
between the most recent inflection point event and pulling of payout
lever were banked nanoseconds before the real deal inflection point,
the preemption decision.
-Mike
next prev parent reply other threads:[~2026-11-03 5:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 13:03 Chengfeng Lin
2026-10-30 17:01 ` Mike Galbraith
2026-11-01 14:37 ` Chengfeng Lin
2026-11-01 17:46 ` Mike Galbraith
2026-11-02 7:58 ` Chengfeng Lin
2026-11-03 5:28 ` Mike Galbraith [this message]
2026-11-03 7:07 ` Tianchen Ding
2026-11-03 9:46 ` Chengfeng Lin
-- strict thread matches above, loose matches on Subject: below --
2026-06-05 12:40 [PATCH v3 0/7] sched: Flatten the pick Peter Zijlstra
2026-06-05 12:40 ` [PATCH v3 7/7] sched/eevdf: Move to a single runqueue Peter Zijlstra
2026-06-20 3:54 ` Chen, Yu C
2026-06-26 11:40 ` Peter Zijlstra
2026-06-29 14:02 ` Vincent Guittot
2026-10-16 13:18 ` Jakub Okoński
2026-10-18 6:49 ` Mike Galbraith
2026-10-19 17:01 ` Vincent Guittot
2026-10-19 17:35 ` Jakub Okoński
2026-10-19 18:04 ` Vincent Guittot
2026-10-19 18:24 ` Jakub Okoński
2026-10-19 18:26 ` Vincent Guittot
2026-10-21 11:55 ` Vincent Guittot
2026-10-22 12:05 ` Jakub Okoński
2026-10-30 15:48 ` Chengfeng Lin
2026-10-22 2:12 ` Mike Galbraith
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=41ac0a8e95e22870efe308e8df9921960c53d4bc.camel@gmx.de \
--to=efault@gmx.de \
--cc=juri.lelli@redhat.com \
--cc=lin2530632123@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®