From: Raistlin <raistlin@linux.it>
To: Chris Friesen <cfriesen@nortel.com>
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>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: massive_intr on CFS, BFS, and EDF
Date: Sat, 26 Sep 2009 08:50:26 +0200 [thread overview]
Message-ID: <1253947826.4924.9.camel@Palantir> (raw)
In-Reply-To: <4ABD36CE.3080400@nortel.com>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
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?
>
What I want is the user to be able to achieve whatever result he likes.
Thus, with EDF_GROUP_SCHED enabled, you first have to assign a bandwidth
value, at least to the root group. If 100% (e.g., on UP) is used as such
value, oversubscription will never happen.
If EDF_GROUP_SCHED is off, nothing is in place right now, but I already
planned to add it, and I'm just introducing something like
sysctl_sched_rt_runtime, sysctl_sched_rt_period, in the new version I'm
working on right now.
> If you have massive oversubscription with EDF, what is the design
> intent? Do you try to meet the goals on as many tasks as possible,
> while the oversubscribed tasks get nothing?
>
No, nothing like that... So using this scheduler without avoiding system
overload will be nonsene, unless some kind of logic (as you was
describing) is not implemented in userspace, and that's why I think
oversubscription avoidance should be an available, but also,
configurrable feature... Comments on that?
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 --]
prev parent reply other threads:[~2009-09-26 6:50 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
2009-09-26 6:50 ` Raistlin [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=1253947826.4924.9.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