2.4.10-ac10-preempt lmbench output.
Quoted 5 lines · Andrea Arcangeli
Quoted 4 lines · Robert Love
Quoted 3 lines · Andrea Arcangeli
As said it's very very unlikely that preemption points can fix xmms skips anyways, the worst scheduler latency is always of the order of the msecs, to generate skips you need a latency of seconds.
[...]
Quoted 4 lines
The point is that to avoid dropouts dbench must take say 40% of the cpu and xmms another 40% of the cpu. Then the 10msec doesn't matter. If each one takes 50% of cpu exactly you can run in dropouts anyways because of scheduler imprecisions.
I get the dropouts (2~3 sec) after dbench 32 is running for 9~10 seconds. I've tried with RT artds and nice -20 mpg123.
Kernel: 2.4.11-pre6 + 00_vm-1 + preempt
Only solution:
I have to copy the test MPG3 file into /dev/shm.
CPU (1 GHz Athlon II) is ~75% idle during the hiccup.
The dbench processes are mostly in wait_page/wait_cache if I remember right. So I think that you are right it is a file IO wait (latency) problem.
Please hurry up with your read/write copy-user paths lowlatency patches ;-)
Quoted 7 lines
So again: the preemptive patch cannot make any difference, except for the read/write copy-user paths that originally Ingo fixed ages ago in 2.2, and that I also later fixed in all -aa 2.2 and 2.4 and that are also fixed in the lowlatency patches from Andrew (but in the generic_file_read/write rather than in copy-user, to possible avoid some overhead for short copy users, but the end result for an xmms user is exactly the same).
Andrew have you a current version of your lowlatency patches handy?
Robert you are running a dual PIII system, right?
Could that be the ground why you aren't see the hiccup with your nice preempt patch? Are you running ReiserFS or EXT2/3?
Thanks,
Dieter