From: Rik van Riel <riel@surriel.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Paul Turner <pjt@google.com>,
"vincent.guittot" <vincent.guittot@linaro.org>,
kernel-team@fb.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dietmar.eggeman" <dietmar.eggeman@arm.com>
Subject: Re: CFS flat runqueue proposal fixes/update
Date: Fri, 07 Aug 2020 15:41:57 -0400 [thread overview]
Message-ID: <9ed51691d4e129b5c30343a89a107d4ff9dd89ce.camel@surriel.com> (raw)
In-Reply-To: <1eaeeb1d-96c7-4819-8e1e-8f190a650030@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
On Fri, 2020-08-07 at 16:14 +0200, Dietmar Eggemann wrote:
> On 31/07/2020 09:42, Rik van Riel wrote:
> > Possible solution
> > ...
> I imagine that I can see what you want to achieve here ;-)
>
> But it's hard since your v5 RFC
> https://lkml.kernel.org/r/20190906191237.27006-1-riel@surriel.com is
> pretty old by now.
The v5 patches also do not implement this new idea, and
still suffer from the corner cases that Paul Turner
pointed out last year.
> Do you have a version of the patch-set against tip/sched/core? Quite
> a
> lot has changed (runnable load avg replaced by runnable avg, rq->load
> is
> gone, CFS load balance rework).
Not yet. We got a baby this spring, so I've been busy
with things like milk and diapers, instead of with
code.
I wanted to get this proposal out before Plumbers, so
we could at least talk about it, and maybe find flaws
with this idea before I spend weeks/months implementing it :)
> IMHO it would be extremely helpful to have a current patch-set to
> discuss how these other problems can be covered by patches on top.
Agreed. I hope to get some time to work on that, but
no guarantees about getting it ready before Plumbers :)
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-07 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 7:42 Rik van Riel
2020-08-07 14:14 ` Dietmar Eggemann
2020-08-07 19:41 ` Rik van Riel [this message]
2020-08-20 14:56 ` Dietmar Eggemann
2020-08-20 20:39 ` Rik van Riel
2020-08-21 17:53 ` Dietmar Eggemann
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=9ed51691d4e129b5c30343a89a107d4ff9dd89ce.camel@surriel.com \
--to=riel@surriel.com \
--cc=dietmar.eggeman@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--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®