From: Peter Zijlstra <peterz@infradead.org>
To: Alessio Balsini <a.balsini@sssup.it>
Cc: Ingo Molnar <mingo@redhat.com>,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
Juri Lelli <juri.lelli@arm.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andrea Parri <parri.andrea@gmail.com>,
Luca Abeni <luca.abeni@santannapisa.it>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] sched/deadline: Hierarchical scheduling with DL on top of RT
Date: Fri, 31 Mar 2017 19:51:19 +0200 [thread overview]
Message-ID: <20170331175119.kvceyujurwofxzym@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1490982277-4437-3-git-send-email-a.balsini@sssup.it>
On Fri, Mar 31, 2017 at 07:44:36PM +0200, Alessio Balsini wrote:
> The runtime of RT tasks controlled by CGroups are enforced by the
> SCHED_DEADLINE scheduling class, based on the runtime and period (the
> deadline is set equal to the period) parameters.
>
> sched_dl_entity may also represent a group of RT tasks, providing a rt_rq.
Such a short changelog for such a big patch..
What does it do with RT affinities and AC ?
Does it do the minimal concurrency thing; or something else? All things
that should be explained and are not.
next prev parent reply other threads:[~2017-03-31 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 17:44 [RFC PATCH 0/3] RT bandwidth constraints enforced by hierarchical DL scheduling Alessio Balsini
2017-03-31 17:44 ` [RFC PATCH 1/3] sched/rt: Removed CGroup functionalities from RT scheduling class Alessio Balsini
2017-03-31 17:44 ` [RFC PATCH 2/3] sched/deadline: Hierarchical scheduling with DL on top of RT Alessio Balsini
2017-03-31 17:51 ` Peter Zijlstra [this message]
2017-03-31 17:44 ` [RFC PATCH 3/3] sched/rt: DL-RT group migration from throttled rq Alessio Balsini
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=20170331175119.kvceyujurwofxzym@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=a.balsini@sssup.it \
--cc=bristot@redhat.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@redhat.com \
--cc=parri.andrea@gmail.com \
--cc=rostedt@goodmis.org \
--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 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®