Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.9

[Rui Nuno Capela]

Ingo Molnar wrote:
>
> ah ... found it - a fair portion of spinlocks and rwlocks had deadlock
> detection turned off in -V0.6.6 - amongst them ptype_lock. I've uploaded
> -V0.6.9 that fixes this.
>

OK. Already tested RT-V0.6.9 and things are really good, so far. Got it
under the jackd-R + 9*fluidsynth workload test, and the comparison to
2.6.9 (vanilla) is getting kind of humiliating :)

                                   2.6.9   RT-V0.6.9
                                 --------- ---------
 XRUN Rate   . . . . . . . . . :    415         0    /hour
 Delay Rate (>spare time)  . . :    493         0    /hour
 Delay Rate (>1000 usecs)  . . :    913         1    /hour
 Delay Maximum . . . . . . . . :   6877       864    usecs
 Cycle Maximum . . . . . . . . :   1440      1552    usecs
 Average DSP Load. . . . . . . :     38.9      40.5  %
 Average Interrupt Rate  . . . :   1337      1338    /sec
 Average Context-Switch Rate . :   7488      9048    /sec

As before, these stats were taken by running jackd -v -dalsa -dhw:0
-r44100 -p128 -n2 -S -P, loaded with 9 (nine) fluidsynth instances, on a
P4@xxxxxxxx laptop, against the onboard sound device (snd-ali5451).
The results were averaged for 12 consecutive runs of 5 minutes each.

On the RT kernel, the IRQ 5 handler thread, that serves the ali5451 sound
device, has been chrt'ed to SCHED_FIFO and to priority=60 (chrt -p -f 60
`pidof "IRQ 5"`). This time thought, I haven't touched the ksoftirqd/0
scheduling policy nor priority.

I am also rehearsing these same tests on my P4/SMT desktop. I'll post
those a bit later today.

As a personal comment, I've never, never seen so good figures in any other
kernel I've came across in the last couple of years. I hope this can only
go to the better ;)

See ya.
-- 
rncbc aka Rui Nuno Capela
rncbc@xxxxxxxxx

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/