[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1208867154.4873.4.camel@marge.simson.net>
Date: Tue, 22 Apr 2008 14:25:54 +0200
From: Mike Galbraith <efault@....de>
To: Ingo Molnar <mingo@...e.hu>
Cc: Frans Pop <elendil@...net.nl>, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Richard Jonsson <richie@...erworld.net>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [git pull] scheduler changes for v2.6.26
On Tue, 2008-04-22 at 10:59 +0200, Ingo Molnar wrote:
> * Mike Galbraith <efault@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists