From: luca abeni <luca.abeni@unitn.it>
To: Peter Zijlstra <peterz@infradead.org>
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 08:38:57 +0200 [thread overview]
Message-ID: <20161017083857.4833d539@utopia> (raw)
In-Reply-To: <20161016214059.65ac35b6@utopia>
On Sun, 16 Oct 2016 21:40:59 +0200
Luca Abeni <luca.abeni@unitn.it> wrote:
> On Mon, 10 Oct 2016 13:08:18 +0200
> Peter Zijlstra <peterz@infradead.org> wrote:
>
> > 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.
> Yes, there currently is no existing schedulability analysis for
> multi-processor EDF with random affinities (as far as I know)
Correction: it looks like I was wrong, and the schedulability of
multi-processor EDF with arbitrary affinities has already been analysed
in
A. Gujarati, F. Cerqueira, and B. Brandenburg, “Multiprocessor
Real-Time Scheduling with Arbitrary Processor Affinities: From Practice
to Theory”, Real- Time Systems, Volume 51, Issue 4, pp. 440–483.
Springer Verlag, 2015
(see https://www.mpi-sws.org/~bbb/papers/).
Thanks to Giuseppe Lipari for pointing me to this paper.
So, having DL tasks with arbitrary affinities is not a big problem from
the theoretical point of view... The only issue is that the
utilisation-based admission test that is currently implemented in the
kernel does not work (and given the complexity of the analysis I think
it is better not to perform it in the kernel :)
Luca
> but I
> think we can at least have a look at developing this kind of analysis.
> Giuseppe, what do you think?
next prev parent reply other threads:[~2016-10-17 6:39 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 [this message]
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=20161017083857.4833d539@utopia \
--to=luca.abeni@unitn.it \
--cc=claudio@evidence.eu.com \
--cc=giuseppe.lipari@lsv.ens-cachan.fr \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--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.