From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: "Guillaume Chazarain" <guichaz@yahoo.fr>
Cc: "Ingo Molnar" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
a.p.zijlstra@chello.nl, dhaval@linux.vnet.ibm.com
Subject: Re: High wake up latencies with FAIR_USER_SCHED
Date: Tue, 29 Jan 2008 21:56:58 +0530 [thread overview]
Message-ID: <20080129162658.GN1044@linux.vnet.ibm.com> (raw)
In-Reply-To: <3d8471ca0801290753j481c658bud39c541128f3f005@mail.gmail.com>
On Tue, Jan 29, 2008 at 04:53:56PM +0100, Guillaume Chazarain wrote:
> I just thought about something to restore low latencies with
> FAIR_GROUP_SCHED, but it's possibly utter nonsense, so bear with me
> ;-) The idea would be to reverse the trees upside down. The scheduler
> would only see tasks (on the leaves) so could apply its interactivity
> magic, but the hierarchical groups would be used to compute dynamic
> loads for each task according to their position in the tree:
I think this is equivalent to flattening the hierarchy? We discussed this a bit
sometime back [1], but one of its weaknesses is providing strong
partitioning between groups when it comes to ensuring fairness. Ex: imagine a
group which does a fork-bomb. With the flattened tree, it affects other groups
more than it would with a 1-level deep hierarchy.
Having said that, I would be interested to hear other solutions that maintain
this good partitioning b/n groups and still provide good interactivity!
1. http://lkml.org/lkml/2007/5/30/300
> - now:
> - we schedule each level of the tree starting from the root
>
> - with my proposition:
> - we schedule tasks like with !FAIR_GROUP_SCHED, but
> calc_delta_fair() would traverse the tree starting from the leaves to
> compute the dynamic load.
--
Regards,
vatsa
next prev parent reply other threads:[~2008-01-29 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 20:01 High wake up latencies with FAIR_USER_SCHED Guillaume Chazarain
2008-01-28 2:31 ` Srivatsa Vaddagiri
2008-01-28 12:27 ` Ingo Molnar
2008-01-28 16:57 ` Guillaume Chazarain
2008-01-28 20:13 ` Guillaume Chazarain
2008-01-29 5:47 ` Srivatsa Vaddagiri
2008-01-29 15:53 ` Guillaume Chazarain
2008-01-29 16:26 ` Srivatsa Vaddagiri [this message]
2008-01-31 10:47 ` Peter Zijlstra
2008-01-31 12:49 ` Guillaume Chazarain
2008-01-31 13:00 ` Peter Zijlstra
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=20080129162658.GN1044@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=guichaz@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.