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: <20080423094644.GB23293@elte.hu>
Date:	Wed, 23 Apr 2008 11:46:44 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frans Pop <elendil@...net.nl>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org, Mike Galbraith <efault@....de>,
	Richard Jonsson <richie@...erworld.net>
Subject: Re: [git pull] scheduler changes for v2.6.26

* Frans Pop <elendil@...net.nl> wrote:

> If I enable tracing with these settings, I get data in both trace 
> *and* in latency_trace. Is the last correct? From 
> http://lkml.org/lkml/2008/2/10/43 I got the impression that file 
> should only be used if the "wakeup" tracer is active.

yeah, that's the intended behavior. 'trace' and 'latency_trace' are two 
kinds of 'views' on the same set of tracer data (with a different output 
format). They are both non-destructive - i.e. they dont deplete the 
trace buffers.

there's even a third view: 'trace_pipe' - which depletes the trace 
buffers and can be used to pipe trace data into a larger file:

    cat trace_pipe > /tmp/large-trace.txt

i guess it would be less confusing if 'trace' and 'latency_trace' was 
just a single 'view' and its behavior depended on iter_ctl settings. (In 
fact, we could probably just get rid of latency_trace - it is a leftover 
from -rt.)

> From the last run I've got three traces with 50000 entries (about a 
> minute worth each). Traces 1 and 2 should each have two skips and 
> trace 3 should have four. I've saved both the trace and latency_trace 
> (ltrace) files.
> 
> They are available at: 
> http://people.debian.org/~fjp/tmp/kernel/sched/.

thanks, we'll have a look.

> BTW, did either of you actually look at the traces I sent for .24? I 
> never got any feedback on those.

hm, i looked at them - i thought i mailed you about that but indeed i 
didnt (sorry about that) - the traces were too short in scope - they 
just covered a few dozen milliseconds in scope, while your description 
said that the problem occured seconds into the trace.

> P.S. I've got group scheduling active in this config as my tests with 
> .24 showed that did not make any difference. Can rerun without if 
> needed.

no need to rerun - but if you do the next test it might make sense to 
disable it, just to reduce the number of variables.

another thing - Peter observed skipping on NOHZ. Does your skipping go 
away if you boot with 'nohz' and/or with CONFIG_NOHZ=y disabled in the 
.config?

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