From: Peter Zijlstra <peterz@infradead.org>
To: Luca Abeni <luca.abeni@unitn.it>
Cc: linux-kernel@vger.kernel.org,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
Juri Lelli <juri.lelli@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrea Parri <parri.andrea@gmail.com>
Subject: Re: About group scheduling for SCHED_DEADLINE
Date: Mon, 10 Oct 2016 13:08:18 +0200 [thread overview]
Message-ID: <20161010110818.GA11311@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20161010101558.GL3568@worktop.programming.kicks-ass.net>
On Mon, Oct 10, 2016 at 12:15:58PM +0200, Peter Zijlstra wrote:
> However, I think there's a third alternative. I have memories of a paper
> from UNC (I'd have to dig through the site to see if I can still find
> it) where they argue that for a hierarchical (G-)FIFO you should use
> minimal concurrency, that is run the minimal number of (v)cpu servers.
>
> This would mean we give a single CBS parameter and carve out the minimal
> number (of max CBS) (v)cpu that fit in that.
>
> I'm just not sure how the random affinity crap works out for that, if we
> have the (v)cpu servers migratable in the G-EDF and migrate to whatever
> is demanded by the task at runtime it might work, but who knows..
> Analysis would be needed I think.
Hurm,.. thinking slightly more on this, this ends up being a DL task
with random affinity, which is problematic IIRC.
next prev parent reply other threads:[~2016-10-10 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 19:39 About group scheduling for SCHED_DEADLINE Luca Abeni
2016-10-10 10:15 ` Peter Zijlstra
2016-10-10 11:08 ` Peter Zijlstra [this message]
2016-10-16 19:40 ` Luca Abeni
2016-10-17 6:38 ` luca abeni
2016-10-17 8:25 ` Peter Zijlstra
2016-10-18 9:43 ` Juri Lelli
2016-10-10 12:04 ` Peter Zijlstra
2016-10-16 19:34 ` Luca Abeni
2016-10-17 10:52 ` 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=20161010110818.GA11311@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=parri.andrea@gmail.com \
--cc=tglx@linutronix.de \
--cc=tommaso.cucinotta@sssup.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.