From: Peter Zijlstra <peterz@infradead.org>
To: Juri Lelli <juri.lelli@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, rostedt@goodmis.org,
oleg@redhat.com, fweisbec@gmail.com, darren@dvhart.com,
johan.eker@ericsson.com, p.faure@akatech.ch,
linux-kernel@vger.kernel.org, claudio@evidence.eu.com,
michael@amarulasolutions.com, fchecconi@gmail.com,
tommaso.cucinotta@sssup.it, nicola.manica@disi.unitn.it,
luca.abeni@unitn.it, dhaval.giani@gmail.com, hgu1972@gmail.com,
paulmck@linux.vnet.ibm.com, raistlin@linux.it,
insop.song@ericsson.com, liming.wang@windriver.com,
jkacur@redhat.com, harald.gustafsson@ericsson.com
Subject: Re: [RFC][PATCH 00/15] sched: SCHED_DEADLINE v5
Date: Tue, 29 May 2012 12:07:18 +0200 [thread overview]
Message-ID: <1338286038.26856.20.camel@twins> (raw)
In-Reply-To: <4FC34011.4040505@gmail.com>
On Mon, 2012-05-28 at 11:06 +0200, Juri Lelli wrote:
> o The only "big problem" I fear is related to the current deadline
> inheritance mechanism. As Steven pointed out during the last review,
> a task could force more bandwidth than was allowed if:
>
> - it takes a futex;
> - it is boosted while holding it;
> - never releases the futex;
>
> and this is sadly achievable since, if boosted, a task inherits top
> waiter parameters and the enforcement mechanism is temporarily
> disabled for it.
/me goes read patch 12 in detail..
Wouldn't it be possible to enforce pi_se (aka. pi_task)'s bandwidth in
the dl-boosts-dl case?
Since afaict that's the only case we need to worry about. If you can
spawn FIFO/RR tasks you already loose bandwidth caps etc..
prev parent reply other threads:[~2012-05-29 10:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 21:42 [RFC][PATCH 00/15] sched: SCHED_DEADLINE v5 Juri Lelli
2012-05-23 21:42 ` [PATCH 01/15] math128: Introduce various 128bit primitives Juri Lelli
2012-05-23 21:42 ` [PATCH 02/15] math128, x86_64: Implement {mul,add}_u128 in 64bit asm Juri Lelli
2012-05-23 21:42 ` [PATCH 03/15] sched: add sched_class->task_dead Juri Lelli
2012-05-23 21:42 ` [PATCH 04/15] sched: add extended scheduling interface Juri Lelli
2012-05-23 21:42 ` [PATCH 05/15] sched: SCHED_DEADLINE structures & implementation Juri Lelli
2012-05-23 21:42 ` [PATCH 06/15] sched: SCHED_DEADLINE SMP-related data structures & logic Juri Lelli
2012-05-23 21:42 ` [PATCH 07/15] sched: SCHED_DEADLINE avg_update accounting Juri Lelli
2012-05-23 21:42 ` [PATCH 08/15] sched: add period support for -deadline tasks Juri Lelli
2012-05-23 21:42 ` [PATCH 09/15] sched: add schedstats " Juri Lelli
2012-05-23 21:42 ` [PATCH 10/15] sched: add latency tracing " Juri Lelli
2012-05-23 21:42 ` [PATCH 11/15] rtmutex: turn the plist into an rb-tree Juri Lelli
2012-05-23 21:42 ` [PATCH 12/15] sched: drafted deadline inheritance logic Juri Lelli
2012-05-23 21:42 ` [PATCH 13/15] sched: add bandwidth management for sched_dl Juri Lelli
2012-05-25 10:38 ` Peter Zijlstra
2012-05-26 11:07 ` Juri Lelli
2012-05-29 9:58 ` Peter Zijlstra
2012-05-29 12:18 ` Juri Lelli
2012-05-29 12:31 ` Peter Zijlstra
2012-05-30 15:34 ` Juri Lelli
2012-05-23 21:42 ` [PATCH 14/15] sched: speed up -dl pushes with a push-heap Juri Lelli
2012-05-23 21:42 ` [PATCH 15/15] sched: add sched_dl documentation Juri Lelli
2012-05-25 10:42 ` [RFC][PATCH 00/15] sched: SCHED_DEADLINE v5 Peter Zijlstra
2012-05-25 11:04 ` Thomas Gleixner
2012-05-28 9:06 ` Juri Lelli
2012-05-29 10:07 ` 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=1338286038.26856.20.camel@twins \
--to=peterz@infradead.org \
--cc=claudio@evidence.eu.com \
--cc=darren@dvhart.com \
--cc=dhaval.giani@gmail.com \
--cc=fchecconi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=harald.gustafsson@ericsson.com \
--cc=hgu1972@gmail.com \
--cc=insop.song@ericsson.com \
--cc=jkacur@redhat.com \
--cc=johan.eker@ericsson.com \
--cc=juri.lelli@gmail.com \
--cc=liming.wang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=michael@amarulasolutions.com \
--cc=mingo@redhat.com \
--cc=nicola.manica@disi.unitn.it \
--cc=oleg@redhat.com \
--cc=p.faure@akatech.ch \
--cc=paulmck@linux.vnet.ibm.com \
--cc=raistlin@linux.it \
--cc=rostedt@goodmis.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.