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>,
giuseppe lipari <giuseppe.lipari@lsv.ens-cachan.fr>,
Claudio Scordino <claudio@evidence.eu.com>
Subject: Re: About group scheduling for SCHED_DEADLINE
Date: Mon, 17 Oct 2016 12:52:50 +0200 [thread overview]
Message-ID: <20161017105250.GP3117@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20161016213420.64b772da@utopia>
On Sun, Oct 16, 2016 at 09:34:20PM +0200, Luca Abeni wrote:
> Hi Peter,
>
> first of all, sorry for the delay in my answer
Not a problem, we're all busy. As it happens I had this thing in Berlin
which delayed me reading email in any case ;-)
> > 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.
> Ok, I need to find and read that paper
I had a real quick look and it could be this one, but memories are
vague...
https://cs.unc.edu/~anderson/papers/ecrts08c.pdf
In particular 3.P.
prev parent reply other threads:[~2016-10-17 10:53 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
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 [this message]
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=20161017105250.GP3117@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=claudio@evidence.eu.com \
--cc=giuseppe.lipari@lsv.ens-cachan.fr \
--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.