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

[Frans Pop <elendil@planet.nl>]

On Wednesday 23 April 2008, you wrote:
> > 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.

Ah, I was wondering about that. Sorry about the mistake, but if you'd let me 
know I could have run new traces.

If there's anything wrong with the current traces, please _do_ let me know. 
Problem is that I just see a huge pile of data without really knowing what 
I'm looking at. For example, I've no idea what the time units are. If I've 
guessed those wrong, it's not surprising that you don't see anything as I'm 
then basically stopping the trace too late or including too few entries.

What would be a good value for trace_entries to get a decent time interval?

If there's more documentation available about what's in those files, please 
let me know.

Cheers,
FJP

P.S. It would probably be good to just mention the units in the headers of 
the debug files. It may be obvious to you, but that way it's obvious even 
to morons like me :-P