From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Con Kolivas <kernel@kolivas.org>, Nick Piggin <npiggin@suse.de>,
Arjan van de Ven <arjan@infradead.org>,
Peter Williams <pwil3058@bigpond.net.au>,
Thomas Gleixner <tglx@linutronix.de>,
caglar@pardus.org.tr, Willy Tarreau <w@1wt.eu>,
Gene Heskett <gene.heskett@gmail.com>, Mark Lord <lkml@rtr.ca>
Subject: Re: [patch] CFS scheduler, -v10
Date: Tue, 08 May 2007 10:32:09 +0200 [thread overview]
Message-ID: <1178613129.6181.4.camel@Homer.simpson.net> (raw)
In-Reply-To: <1178610698.7558.48.camel@Homer.simpson.net>
On Tue, 2007-05-08 at 09:51 +0200, Mike Galbraith wrote:
> When thud starts, chew takes a size 14EEE latency hit if bits 1, 2 and 3
> are set in sysctl_sched_load_smoothing.
Well shoot, I take it back. I'm seeing it with 0x1 as well.
pid 6155, prio 0, out for 32 ms, ran for 4 ms, load 13%
pid 6155, prio 0, out for 24 ms, ran for 5 ms, load 19%
pid 6155, prio 0, out for 2 ms, ran for 4 ms, load 69%
pid 6155, prio 0, out for 760 ms, ran for 10031 ms, load 92%
pid 6155, prio 0, out for 32 ms, ran for 4 ms, load 13%
pid 6155, prio 0, out for 32 ms, ran for 4 ms, load 13%
next prev parent reply other threads:[~2007-05-08 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 16:33 [patch] CFS scheduler, -v10 Ingo Molnar
2007-05-07 18:35 ` James Cloos
2007-05-07 18:40 ` Ingo Molnar
2007-05-07 19:32 ` James Cloos
2007-05-07 18:49 ` James Cloos
2007-05-07 20:43 ` Paolo Ciarrocchi
2007-05-08 0:47 ` Fortier,Vincent [Montreal]
2007-05-08 7:51 ` Mike Galbraith
2007-05-08 8:32 ` Mike Galbraith [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-09 11:21 Al Boldi
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=1178613129.6181.4.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=caglar@pardus.org.tr \
--cc=gene.heskett@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=pwil3058@bigpond.net.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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