From: "Chris Friesen" <cfriesen@nortel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Michael Trimarchi <trimarchi@gandalf.sssup.it>,
sat <takeuchi_satoru@jp.fujitsu.com>,
lkml <linux-kernel@vger.kernel.org>,
Con Kolivas <kernel@kolivas.org>, Ingo Molnar <mingo@elte.hu>,
Raistlin <raistlin@linux.it>
Subject: Re: massive_intr on CFS, BFS, and EDF
Date: Fri, 25 Sep 2009 16:46:17 -0600 [thread overview]
Message-ID: <4ABD4839.7060508@nortel.com> (raw)
In-Reply-To: <1253918258.18939.192.camel@laptop>
On 09/25/2009 04:37 PM, Peter Zijlstra wrote:
> On Fri, 2009-09-25 at 15:31 -0600, Chris Friesen wrote:
>> Do you allow oversubscription with EDF? It would seem so based on these
>> results. Would it maybe make sense to disallow oversubscription, or
>> make it an option?
>
> afaiu he doesn't, he simply splits the task's wcet between parent and
> child and (intends?) to feed back on child exit.
How does this work if we have one parent task that forks off a bunch of
kids like massive_intr? Does each child get half the bandwidth of the
previous child?
> oversubscribing edf isn't in general recommended, iirc u>1 gives
> unbounded latencies with edf.
Right...so would it perhaps be more interesting to try a modified test
where each child's bandwidth is equal and small enough that there is no
oversubscription?
Chris
next prev parent reply other threads:[~2009-09-25 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 23:53 massive_intr on CFS, BFS, and EDF sat
2009-09-25 3:27 ` Satoru Takeuchi
2009-09-25 5:35 ` Raistlin
2009-09-25 5:35 ` Raistlin
2009-09-25 16:07 ` Michael Trimarchi
2009-09-25 21:31 ` Chris Friesen
2009-09-25 22:37 ` Peter Zijlstra
2009-09-25 22:46 ` Chris Friesen [this message]
2009-09-26 7:22 ` Raistlin
2009-09-26 6:56 ` Raistlin
2009-09-26 6:50 ` Raistlin
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=4ABD4839.7060508@nortel.com \
--to=cfriesen@nortel.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=takeuchi_satoru@jp.fujitsu.com \
--cc=trimarchi@gandalf.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