From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frans Pop <elendil@planet.nl>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Richard Jonsson <richie@coderworld.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [git pull] scheduler changes for v2.6.26
Date: Tue, 22 Apr 2008 14:25:54 +0200 [thread overview]
Message-ID: <1208867154.4873.4.camel@marge.simson.net> (raw)
In-Reply-To: <20080422085905.GA9939@elte.hu>
On Tue, 2008-04-22 at 10:59 +0200, Ingo Molnar wrote:
> * Mike Galbraith <efault@gmx.de> wrote:
>
> > > the 700-800 msecs of delays you see are very "brutal" so there must
> > > be something fundamentally wrong going on here.
> >
> > I'm seeing latency hits with 26.git, whereas 25 is hit free.
>
> ok. I think what happens is that your broken sched-clock hid the real
> breakage. Lets try fix the real breakage now.
>
> I've uploaded a new sched-devel.git that is against very latest -git,
> could you try ftrace (with a sufficiently large
> /debug/tracing/tracing_max_entries value) - perhaps the
> worst-case-wakeup-latency tracer shows large latencies? If not, then
> maybe the sched_switch tracer gives a better insight into what's
> happening?
Well, looks like this is going to have to wait. sched-devel is locking
hard on me, both sched-devel and .git are losing my darn keyboard right
in the middle of things, and my serial ports are (still) so screwed up I
can't get minicom working right. Arg.
-Mike
next prev parent reply other threads:[~2008-04-22 12:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 18:13 [git pull] scheduler changes for v2.6.26 Ingo Molnar
2008-04-19 18:47 ` Guillaume Chazarain
2008-04-19 18:49 ` Ingo Molnar
2008-04-19 18:54 ` Peter Zijlstra
2008-04-19 19:47 ` Frans Pop
2008-04-21 12:39 ` Ingo Molnar
2008-04-21 16:31 ` Frans Pop
2008-04-21 19:43 ` Ingo Molnar
2008-04-22 8:51 ` Mike Galbraith
2008-04-22 8:59 ` Ingo Molnar
2008-04-22 9:59 ` Peter Zijlstra
2008-04-22 12:25 ` Mike Galbraith [this message]
2008-04-23 8:11 ` Mike Galbraith
2008-04-23 10:30 ` Mike Galbraith
2008-04-23 11:21 ` Peter Zijlstra
2008-04-23 13:27 ` Mike Galbraith
2008-04-22 9:41 ` Kevin Winchester
2008-04-22 10:49 ` David Miller
2008-04-22 11:10 ` Peter Zijlstra
2008-04-23 9:36 ` Frans Pop
2008-04-23 9:42 ` Peter Zijlstra
2008-04-23 9:46 ` Ingo Molnar
2008-04-23 13:36 ` Frans Pop
2008-04-29 12:29 ` Ingo Molnar
2008-04-29 15:28 ` Steven Rostedt
2008-04-23 16:23 ` Frans Pop
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=1208867154.4873.4.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=richie@coderworld.net \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
/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