The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dhaval Giani <dhaval@linux.vnet.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: revert load_balance_monitor()
Date: Thu, 28 Feb 2008 17:13:11 +0100	[thread overview]
Message-ID: <1204215191.4319.7.camel@homer.simson.net> (raw)
In-Reply-To: <20080228132627.GA24096@elte.hu>


On Thu, 2008-02-28 at 14:26 +0100, Ingo Molnar wrote: 

> Mike, could you check whether today's sched-devel.git (which includes 
> the full revert) works well for you? (with group scheduler enabled)

No, it's fairly lurchy with three root chew-max and one user chew-max
running.  Moving the mouse around while they're running, I can see/feel
the load, and max latency for the user chew-max quickly shoots to
>500ms.

Running the same with mainline + full revert, the load is not palpable
and max latency  for user task was 83ms.

Group CPU distribution otoh is better than mainline git + full revert.

root 
out   16 ms [max:  295, avg:   14, flu:    2, avg_flu:    7], ran for   20 ms
out   16 ms [max:  295, avg:   14, flu:    0, avg_flu:    7], ran for    9 ms
out    5 ms [max:  295, avg:   14, flu:   10, avg_flu:    7], ran for   13 ms
out   33 ms [max:  295, avg:   14, flu:   28, avg_flu:    7], ran for   12 ms
out   12 ms [max:  295, avg:   14, flu:   20, avg_flu:    7], ran for   13 ms
out   16 ms [max:  295, avg:   14, flu:    3, avg_flu:    7], ran for    4 ms
out   21 ms [max:  295, avg:   14, flu:    4, avg_flu:    7], ran for    8 ms

root
out    7 ms [max:  248, avg:   14, flu:    3, avg_flu:    8], ran for    5 ms
out   27 ms [max:  248, avg:   14, flu:   20, avg_flu:    8], ran for   13 ms
out   17 ms [max:  248, avg:   14, flu:   10, avg_flu:    8], ran for    9 ms
out    8 ms [max:  248, avg:   14, flu:    8, avg_flu:    8], ran for    7 ms
out    6 ms [max:  248, avg:   14, flu:    2, avg_flu:    8], ran for    9 ms
out   10 ms [max:  248, avg:   14, flu:    3, avg_flu:    8], ran for   10 ms
out    8 ms [max:  248, avg:   14, flu:    1, avg_flu:    8], ran for   12 ms
out   13 ms [max:  248, avg:   14, flu:    5, avg_flu:    8], ran for    9 ms

root
out   11 ms [max:  366, avg:   14, flu:    2, avg_flu:    6], ran for    7 ms
out   10 ms [max:  366, avg:   14, flu:    1, avg_flu:    6], ran for    5 ms
out   12 ms [max:  366, avg:   14, flu:    1, avg_flu:    6], ran for    9 ms
out   10 ms [max:  366, avg:   14, flu:    1, avg_flu:    6], ran for    8 ms
out   13 ms [max:  366, avg:   14, flu:    2, avg_flu:    6], ran for   13 ms
out   11 ms [max:  366, avg:   14, flu:    2, avg_flu:    6], ran for   13 ms
out    9 ms [max:  366, avg:   14, flu:    2, avg_flu:    6], ran for    9 ms

user
out    3 ms [max:  509, avg:   20, flu:    1, avg_flu:   13], ran for   27 ms
out    2 ms [max:  509, avg:   20, flu:    0, avg_flu:   13], ran for   12 ms
out    2 ms [max:  509, avg:   20, flu:    0, avg_flu:   13], ran for    2 ms
out   25 ms [max:  509, avg:   20, flu:   22, avg_flu:   13], ran for   74 ms
out    3 ms [max:  509, avg:   20, flu:   21, avg_flu:   13], ran for   29 ms
out    6 ms [max:  509, avg:   20, flu:    3, avg_flu:   13], ran for   17 ms
out    5 ms [max:  509, avg:   20, flu:    0, avg_flu:   13], ran for   28 ms
out    2 ms [max:  509, avg:   20, flu:    3, avg_flu:   13], ran for   34 ms

	-Mike






  reply	other threads:[~2008-02-28 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 12:22 [PATCH] sched: revert load_balance_monitor() Peter Zijlstra
2008-02-25 14:29 ` Mike Galbraith
2008-02-25 14:35   ` Dhaval Giani
2008-02-25 14:37     ` Mike Galbraith
2008-02-28 13:26       ` Ingo Molnar
2008-02-28 16:13         ` Mike Galbraith [this message]
2008-02-29  7:11           ` Mike Galbraith
2008-02-25 15:28     ` Peter Zijlstra
2008-02-25 15:53       ` Heiko Carstens
2008-02-25 16:01       ` Srivatsa Vaddagiri
2008-02-25 16:34         ` 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=1204215191.4319.7.camel@homer.simson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vatsa@in.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