[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ae4545e2004395f345ac030635ba72a1e16ec2fe.camel@gmx.de>
Date: Thu, 09 May 2024 07:00:13 +0200
From: Mike Galbraith <efault@....de>
To: Chen Yu <yu.c.chen@...el.com>
Cc: Peter Zijlstra <peterz@...radead.org>, mingo@...hat.com,
juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, bristot@...hat.com, vschneid@...hat.com,
linux-kernel@...r.kernel.org, kprateek.nayak@....com,
wuyun.abel@...edance.com, tglx@...utronix.de, tim.c.chen@...el.com,
yu.c.chen.y@...il.com
Subject: Re: [RFC][PATCH 10/10] sched/eevdf: Use sched_attr::sched_runtime
to set request/slice suggestion
On Thu, 2024-05-09 at 11:48 +0800, Chen Yu wrote:
> And I agree we should take the platform size(such
> as CPU number) into consideration.
I think you'll need more that that, because size agnostic, when it
comes to latency, an idle CPU is damn hard to beat, making migration
restrictions (traditional and obvious target) tend to leave highly
annoying piles of collateral damage in their wake.
(spoken from BTDT perspective, have t-shirt, got butt kicked;)
-Mike
Powered by blists - more mailing lists