linux-kernel - Re: [git pull] scheduler changes for v2.6.26

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1208858363.7115.223.camel@twins>
Date:	Tue, 22 Apr 2008 11:59:23 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Mike Galbraith <efault@....de>, Frans Pop <elendil@...net.nl>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, Richard Jonsson <richie@...erworld.net>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Guillaume Chazarain <guichaz@...oo.fr>
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?
> 
> > Erm, should my Q6600 emit such?
> 
> on nohz it could happen - and fixed in -git. Patch looked too dangerous 
> for late-2.6.25 to merge.

Also, it only happens when the cpu has idle time; and that typically
happens when its well,. idle - so not much to schedule wrong.

That said; yes there are boundary effect that could make it show up.

> > On 26.git, I get numbers like yours, but with occasional dips down to 
> > ~700, though the latency hits don't _seem_ to be synchronous with 
> > watch-rq-clock.sh glitchies.
> 
> hm, the dips shouldnt be happening normally.

Agreed, those ought to be gone.. Guillaume do you see any holes in the
current rq clock code?

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