From: Raistlin <raistlin@linux.it>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Chris Friesen <cfriesen@nortel.com>,
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>
Subject: Re: massive_intr on CFS, BFS, and EDF
Date: Sat, 26 Sep 2009 08:56:11 +0200 [thread overview]
Message-ID: <1253948171.4924.14.camel@Palantir> (raw)
In-Reply-To: <1253918258.18939.192.camel@laptop>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
On Sat, 2009-09-26 at 00:37 +0200, 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,
yeaah, as explained in the previous mail, this is in place only if group
scheduling is on since now, but I'll add these bits to non-group
solution, aalready planned that. :-)
> he simply splits the task's wcet between parent and
> child and (intends?) to feed back on child exit.
>
yes again, that's what the submitted patch does, which is an arbitrary
choice among all the non-optimal solutions I'm able to think of, as
explained in the first e-mail! :-(
Now, I'm going to give your suggestion of assigning children 0 bandwidth
a shot, and ask the parent (they can't they have no bandwidth!) to give
them some runtime/deadline to make them run.
This also has some issues, I think, but looks more natural... At least
does not affect parent's bandwidth, possibly reducing it to (almost)
0!! :-(
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)
http://blog.linux.it/raistlin / raistlin@ekiga.net /
dario.faggioli@jabber.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-09-26 6:56 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
2009-09-26 7:22 ` Raistlin
2009-09-26 6:56 ` Raistlin [this message]
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=1253948171.4924.14.camel@Palantir \
--to=raistlin@linux.it \
--cc=cfriesen@nortel.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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