From: Chris Mason <clm@meta.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>, Chris Mason <clm@fb.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] sched/fair: bump sd->max_newidle_lb_cost when newidle balance fails
Date: Thu, 26 Jun 2025 10:55:20 -0400 [thread overview]
Message-ID: <dbbff170-db0a-4955-a024-978bb8dc3016@meta.com> (raw)
In-Reply-To: <CAKfTPtBE0_77+J-A7vWRKsHCCmuX1jWTbPYWGVPg1MYq_rv8Og@mail.gmail.com>
On 6/26/25 10:26 AM, Vincent Guittot wrote:
> On Thu, 26 Jun 2025 at 12:58, Chris Mason <clm@meta.com> wrote:
>> Got it, I'll play with that. Vincent, was there a benchmark I can use
>> to see if I've regressed the case you were focused on?
>
> It's not a public benchmark but I had some unitary tests with tasks
> waiting on a busy CPU while other CPUs become idle for a "long" time
> (but still less than 500us in average). This is even more true with
> frequency scaling which will minimize the idle duration by decreasing
> the frequency
Ok, I don't think I'll be able to reliably recreate that on my own, can
I ask you to rerun against the v2 I sent out?
-chris
next prev parent reply other threads:[~2025-06-26 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 20:48 Chris Mason
2025-06-26 7:00 ` Peter Zijlstra
2025-06-26 7:44 ` Vincent Guittot
2025-06-26 10:58 ` Chris Mason
2025-06-26 14:26 ` Vincent Guittot
2025-06-26 14:55 ` Chris Mason [this message]
2025-06-27 13:32 ` Vincent Guittot
2025-07-04 15:46 ` Vincent Guittot
2025-06-26 11:47 ` Jianyong Wu
2025-06-26 13:48 ` Chris Mason
2025-06-26 14:02 ` 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=dbbff170-db0a-4955-a024-978bb8dc3016@meta.com \
--to=clm@meta.com \
--cc=clm@fb.com \
--cc=linux-kernel@vger.kernel.org \
--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®