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: Sun, 01 Nov 2026 18:46:43 +0100 [thread overview]
Message-ID: <455d642847fdee6e2a8b594597037c5db9791afa.camel@gmx.de> (raw)
In-Reply-To: <CANGjgd=DvO72NiB8SC3hNEadmxgzy1niN-mnWyY-LGMJ4H=J0g@mail.gmail.com>
On Sun, 2026-11-01 at 22:37 +0800, Chengfeng Lin wrote:
>
> Is this the path you had in mind, or were you referring to a different
> update? I'd be happy to test another candidate change.
Where I see negative impact of the __dequeue_task() update is when
probe components compete in one cgroup, ie pinned wakelat and 8 pinned
hogs used to measure the delta between smp and concur CPU distribution
modes during cgroup vs cgroup testing, all stuffed into one cgroup.
Do whatever you like there, just keep update_curr() far away from
cfs_rq_of(se) and probe goes silent. For virgin flat in isolation,
that was the only signal the probe generated.
-Mike
next prev parent reply other threads:[~2026-11-01 17:46 UTC|newest]
Thread overview: 19+ 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 [this message]
-- 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=455d642847fdee6e2a8b594597037c5db9791afa.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®