mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Guillaume Chazarain" <guichaz@yahoo.fr>
To: vatsa@linux.vnet.ibm.com
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 16:53:56 +0100	[thread overview]
Message-ID: <3d8471ca0801290753j481c658bud39c541128f3f005@mail.gmail.com> (raw)
In-Reply-To: <20080129054742.GA7902@linux.vnet.ibm.com>

On Jan 29, 2008 6:47 AM, Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:

> IMHO this is expected results and if someone really needs to cut down
> this latency, they can reduce sysctl_sched_latency (which will be bad
> from perf standpoint, as we will cause more cache thrashing with that).

Thank you very much for the detailed explanation Srivatsa, that made a
lot of sense. Unfortunately, it means I'll disable FAIR_USER_SCHED as
I initially thought these latencies were caused by my local patches
that give each group a load proportional to the max load of its
elements. Anyway, I don't absolutely need a fair user scheduler on my
laptop, but low latencies in the default configuration are nice to
have.

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:

- 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.

Thanks.

-- 
Guillaume

  reply	other threads:[~2008-01-29 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 20:01 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 [this message]
2008-01-29 16:26           ` Srivatsa Vaddagiri
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=3d8471ca0801290753j481c658bud39c541128f3f005@mail.gmail.com \
    --to=guichaz@yahoo.fr \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vatsa@linux.vnet.ibm.com \
    /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

all inboxes | Powered by JetHome®