2.4.10-ac10-preempt lmbench output.
I'm very pleased so far with ac10 with the preempt patch. Much better than 2.4.9-ac18-preempt, which is what i was using. I'm just going to put up some output from lmbench to see if anyone who is running the non-preempt version
is seeing better or worse timings and scores. Perhaps the improvement is
all in my head due to me moving my atapi devices off of the promise card (since you're not supposed to put any on it) and now everything is generally running faster despite the kernel being used. Heh. so here they are
ftp://ftp.bitmover.com/lmbench/LMbench2.tgz
(top of README says lmbench 2alpha8)
compiled without any changes to the Makefile (gcc 2.95.4)
Simple syscall: 0.3226 microseconds
Simple read: 0.8185 microseconds
Simple write: 0.5791 microseconds
Simple stat: 3.7546 microseconds
Simple open/close: 5.6581 microsecondslat_fs (ext2)
0k 1000 36770 123993 1k 1000 15526 74383 4k 1000 15202 73692 10k 1000 9124 51972
FIFO latency: 8.0457 microseconds
Signal handler installation: 0.932 microseconds
Signal handler overhead: 2.852 microseconds
Protection fault: 0.761 microseconds
Pipe latency: 7.9139 microseconds
Pagefaults on /something.avi: 13098 usecs
Process fork+exit: 249.6818 microseconds
Process fork+execve: 298.0000 microseconds
Process fork+/bin/sh -c: 7883.0000 microsecondsAF_UNIX sock stream latency: 11.0054 microseconds
Select on 200 tcp fd's: 62.7955 microseconds
Select on 200 fd's: 18.5960 microseconds
Fcntl lock latency: 7.3516 microsecondslat_ctx on an Eterm process
"size=0k ovr=2.82
"size=1024k ovr=301.96
That's all from lmbench2. Anyone without the preempt patch using the same kernel care to compare? I'm very pleased.
Heavily io bound processes (dbench 32) still causes something as light as an
mp3 player to skip, though. That probably wont be fixed intil 2.5, since
you need to have preemption in the vm and the rest of the kernel.
Quoted 2 lines · safemode
mp3 player to skip, though. That probably wont be fixed intil 2.5, since
you need to have preemption in the vm and the rest of the kernel.
xmms skips during I/O should have nothing to do with preemption.
As Alan noted for the ring of dma fragments to expire you need a scheduler latency of the order of seconds, now (assuming the ll points in read/write paths) when we've bad latencies under writes it's of the order of 10msec and it can be turned down further by putting preemption checks in the buffer lru lists write paths.
The reason xmms skips I believe is because the vm is doing write throttling. I've at least one idea on how to fix it but it has nothing to do with preemption in the VM or whatever else scheduler related thing.
So I wouldn't expect to fix any playback skips where buffering is possible by using the preemptive patch etc.. It's nearly impossible that it makes any difference.
The preemptive patch can matter only if you're doing real time signal processing where any kind of buffering isn't possible.
Andrea
Quoted 1 line · Andrea Arcangeli
xmms skips during I/O should have nothing to do with preemption.
Why does preemption patch make a difference for me, then? I'm not doing anything even remotely close to real-time processing.
Quoted 5 lines
As Alan noted for the ring of dma fragments to expire you need a scheduler latency of the order of seconds, now (assuming the ll points in read/write paths) when we've bad latencies under writes it's of the order of 10msec and it can be turned down further by putting preemption checks in the buffer lru lists write paths.
Isn't mp3 decoding done `just in time' ie we decode x and buffer x, decode y and buffer y...hopefully in a quick enough manner it sounds like coherent sound? Thus, if the task can not be scheduled as required, there are noticeable latencies in the sound not because the sound card buffer ran dry but because the mp3 couldn't even be decoded to fill the buffer!
Anyhow, if we have latencies of 10ms (and in reality there are higher latencies, too), these can cause the sort of system response scenerios that are a problem. Preemption makes these latencies effectively 0 (outside of locks).
Robert Love
Quoted 17 lines · Andrea Arcangeli
Quoted 2 lines · safemode
mp3 player to skip, though. That probably wont be fixed intil 2.5,
since you need to have preemption in the vm and the rest of the kernel.xmms skips during I/O should have nothing to do with preemption.
As Alan noted for the ring of dma fragments to expire you need a scheduler latency of the order of seconds, now (assuming the ll points in read/write paths) when we've bad latencies under writes it's of the order of 10msec and it can be turned down further by putting preemption checks in the buffer lru lists write paths.
The reason xmms skips I believe is because the vm is doing write throttling. I've at least one idea on how to fix it but it has nothing to do with preemption in the VM or whatever else scheduler related thing.
Quoted 8 lines
So I wouldn't expect to fix any playback skips where buffering is possible by using the preemptive patch etc.. It's nearly impossible that it makes any difference.
The preemptive patch can matter only if you're doing real time signal processing where any kind of buffering isn't possible.
Andrea
That's what i would think too at first. What's confusing me is the fact that it is affected by priority. Which means preemption can solve the problem.
If i run the mp3 player at nice -n -20, i get no skips. Why else would that
be if not that preemption is dictating that freeamp's process gets whatever it wants when it wants ?
My question is why does freeamp need to be at -20 nice just to do it's thing when logic dictates that it should be dbench that skips and is throttled down when run at the same priority as freeamp and not freeamp, since freeamp isn't trying to abuse it's resources.
I mean, if renicing the process allows it not to skip, what else is going on if it's not preemption, isn't that what the purpose of the priorities are - preempting lower priorities? Or is nice something totally different, separate from priorities?
I'm not exactly seeing how renicing it to -20 and the kernel letting freeamp do what it wants over anything else does not fall under the definition of preemption. It cant possibly have nothing to do with preemption of preemption directly effects it.
Ok, so maybe i'm wrong and it has nothing to do with preemption, if then what exactly is allowing freeamp to play perfectly when run with nice -n -20 and
not at normal 0. And why is that the default behavior of the kernel ? It
seems quite unfair in a multiuser-multiprocessing system.
Quoted 22 lines · safemode
Quoted 21 lines · Andrea Arcangeli
Quoted 2 lines · safemode
mp3 player to skip, though. That probably wont be fixed intil 2.5,
since you need to have preemption in the vm and the rest of the kernel.xmms skips during I/O should have nothing to do with preemption.
As Alan noted for the ring of dma fragments to expire you need a scheduler latency of the order of seconds, now (assuming the ll points in read/write paths) when we've bad latencies under writes it's of the order of 10msec and it can be turned down further by putting preemption checks in the buffer lru lists write paths.
The reason xmms skips I believe is because the vm is doing write throttling. I've at least one idea on how to fix it but it has nothing to do with preemption in the VM or whatever else scheduler related thing.
So I wouldn't expect to fix any playback skips where buffering is possible by using the preemptive patch etc.. It's nearly impossible that it makes any difference.
Quoted 8 lines
Quoted 4 lines
The preemptive patch can matter only if you're doing real time signal processing where any kind of buffering isn't possible.
Andrea
That's what i would think too at first. What's confusing me is the fact that it is affected by priority. Which means preemption can solve the problem.
If i run the mp3 player at nice -n -20, i get no skips. Why else would that
As Dan Mann noted privately there's of course also the possibility that the scheduler scheduled xmms away for a long time because there's a very high cpu load, this seems confirmed since the skip goes away with nice -n -20.
Quoted 2 lines
be if not that preemption is dictating that freeamp's process gets whatever it wants when it wants ?
If -n -20 fixes the problem that has nothing to do with scheduler latency or with the write throttling and the preemption patch cannot help at all.
If -n -20 fixes the problem it simply means your cpu load was too high. The linux scheduler is fair. So to fix it there are only those possible ways:
1) buy a faster cpu
2) add additional cpus to your system
3) reduce the cpu load of your system by stopping some of the cpu eaters
4) run xmms RT or with higher priority (or reduce the priority of the other cpu hogs)
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.
I thought your problem weren't just xmms being scheduled away due high cpu load, because dbench is intended to be an I/O benchmark but maybe you've lots of cache and you do little I/O?
The problem I was talking about in my earlier email applies to RT tasks too, so if you were doing lots of I/O and xmms started doing write throttling just running nice -n -20 wouldn't helped.
Quoted 1 line
I mean, if renicing the process allows it not to skip, what else is going on
The reason it allows it not to skip is because the scheduler gives more cpu to xmms.
There's nothing magic in the software, if you divide the cpu in 10 parts and you give 1/10 of the cpu to xmms, but xmms needs 1/2 of the cpu to play your .mp3 then there's nothing you can do to fix it but to tell the scheduler to give more cpu to xmms (renicing to -20 gives more cpu to xmms, enough to sustain the .mp3 decoding without dropouts).
Quoted 1 line
Ok, so maybe i'm wrong and it has nothing to do with preemption, if then what
Correct, it has nothing to do with preemption.
Quoted 2 lines
not at normal 0. And why is that the default behavior of the kernel ? It
seems quite unfair in a multiuser-multiprocessing system.
The opposite, the scheduler is fair, so it divides the cpu to all the tasks in your system. If xmms wouldn't skip the scheduler isn't fair, and as you say that would be very bad in a multiuser system.
Andrea
Quoted 10 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.
[...]
There's nothing magic in the software, if you divide the cpu in 10 parts and you give 1/10 of the cpu to xmms, but xmms needs 1/2 of the cpu to play your .mp3 then there's nothing you can do to fix it but to tell the scheduler to give more cpu to xmms (renicing to -20 gives more cpu
What if the CPU does divide its time into two 1/2 parts, and gives one each to xmms and dbench. Everything runs fine, since xmms needs 1/2 cpu to play without skips.
Now dbench (or any task) is in kernel space for too long. The CPU time xmms needs will of course still be given, but _too late_. Its just not a cpu resource problem, its a timing problem. xmms needs x units of CPU every y units of time. Just getting the x whenever is not enough.
With preempt-kernel patch, the long-lasting kernel space activity dbench is engaged in won't hog the CPU until it completes. When xmms is ready (time y arrives), the scheduler will yield the CPU.
Robert Love
Quoted 5 lines · Robert Love
Quoted 1 line · Andrea Arcangeli
xmms skips during I/O should have nothing to do with preemption.
Why does preemption patch make a difference for me, then? I'm not doing anything even remotely close to real-time processing.
I don't see how can it make any difference with buffered playback of data. It doesn't make sense that it make any difference.
The only factors that can generate xmms skips are:
1) vm write throttling, xmms blocking for seconds during a page fault or while reading the mp3 from disk waiting I/O submitted by another I/O bound application (or also xmms blocking swapping out some page during swapout storms)
I've ideas on how to avoid the write throttling of xmms with heuristics in balance_dirty(), the swapout blocking cannot be avoided instead (it has to block or die)
This problem cannot be avioided from userspace.
2) xmms isn't getting enough cpu, like running xmms on a 386 with 16mhz, it will generate dropouts, run xmms RT or give it the right amount of cpu using priorities to fix the dropouts
3) a scheduler latency of the order of the seconds, the only thing that could generate that could be the read/write paths with lofs of cache
Ah, wait a moment, if the preemptive patch fixes your problem I guess you're hitting the lack of preemption in read/write. I tend to forget about that since I've fixed it ages ago in -aa in both 2.2 and 2.4 by putting the needed preemption points in the copy-users exactly because that could really hang the machine for many seconds on a multi-gb ram box. Andrew suggested to move the scheduler points down to generic_file_read/write and I plan to do that soon.
So could you please check if running -aa or the preemptive patch makes any difference for you while using xmms?
Quoted 7 lines
Quoted 5 lines
As Alan noted for the ring of dma fragments to expire you need a scheduler latency of the order of seconds, now (assuming the ll points in read/write paths) when we've bad latencies under writes it's of the order of 10msec and it can be turned down further by putting preemption checks in the buffer lru lists write paths.
Isn't mp3 decoding done `just in time' ie we decode x and buffer x,
mp3 decoding is done with an huge buffering, this means even if xmms runs after 0.5 sec after it got the wakeup (due scheduler latency problems) it will have no problem to decode the rest of the mp3 and put it in the buffer to the soundcard.
Of course if xmms runs after the soundcard dma ring dried out, then there will be a dropout, but it would need seconds of scheduler latency to generate such a dropout which isn't going to happen.
Of course if you divide the cpu across 100 tasks all cpu hogs, then it is likely xmms will run once every few seconds, (if you assume all tasks are pure cpu hogs it will be a round robin) but that's completly unrelated to the preemption latency.
Quoted 10 lines
decode y and buffer y...hopefully in a quick enough manner it sounds like coherent sound? Thus, if the task can not be scheduled as required, there are noticeable latencies in the sound not because the sound card buffer ran dry but because the mp3 couldn't even be decoded to fill the buffer!
Anyhow, if we have latencies of 10ms (and in reality there are higher latencies, too), these can cause the sort of system response scenerios that are a problem. Preemption makes these latencies effectively 0 (outside of locks).
almost all kernel cpu hogs (except the copy users where I put the reschedule points) that can stall the systems for mseconds are covered by locks. So we need to do stuff like in vmscan.c::shrink_cache also with the preemptive kernel patch, but then calling schedule explicitly won't make any difference in both scheduler latency and performance (it will be actually faster because you do the explicit preemption check only in the cpu hogs rather than in the last spin_unlock.
Andrea
Quoted 7 lines · Robert Love
Quoted 6 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 8 lines
Quoted 4 lines
There's nothing magic in the software, if you divide the cpu in 10 parts and you give 1/10 of the cpu to xmms, but xmms needs 1/2 of the cpu to play your .mp3 then there's nothing you can do to fix it but to tell the scheduler to give more cpu to xmms (renicing to -20 gives more cpu
What if the CPU does divide its time into two 1/2 parts, and gives one each to xmms and dbench. Everything runs fine, since xmms needs 1/2 cpu to play without skips.
Of course. (btw, when running dbench there's usually more than one thread to generate more I/O, usually 20/40, it depends on the parameter but let's assume there's only one thread for the sake of this example)
Quoted 1 line
Now dbench (or any task) is in kernel space for too long. The CPU time
The time in kernel space decreases the timeslice too, so it doesn't matter if it runs in kernel space too long, it will still be accounted as such 1/2 of time.
Quoted 1 line
xmms needs will of course still be given, but
_toolate_. Its just not
I think the issue you raise is that dbench gets a 10msec more of cpu time and xmms starts running 10msec later than expected (because of the scheduler latency peak worst case of 10msec).
But that doesn't matter. The scheduler isn't perfect anyways. The resolution of the scheduler is 10msec too, so you can easily lose 10msec anywhere else no matter of whatever scheduler latency of 10msec.
The only tasks that can get hurted by the scheduler latency are real time tasks running with RT prio that expects to get running in less than 10msec after their wakeup, this is obviously not the xmms case that can live fine even if it becomes running after houndred milliseconds after its wakeup.
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.
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).
So for whatever non real time, but where buffering is possible running lowlatency patch from Ingo or Andrew, preemptive patch, or -aa isn''t going to make any difference.
Quoted 8 lines
a cpu resource problem, its a timing problem. xmms needs x units of CPU every y units of time. Just getting the x whenever is not enough.
With preempt-kernel patch, the long-lasting kernel space activity dbench is engaged in won't hog the CPU until it completes. When xmms is ready (time y arrives), the scheduler will yield the CPU.
Robert Love
Andrea
Quoted 8 lines · Andrea Arcangeli
[...]
I think the issue you raise is that dbench gets a 10msec more of cpu time and xmms starts running 10msec later than expected (because of the scheduler latency peak worst case of 10msec).But that doesn't matter. The scheduler isn't perfect anyways. The resolution of the scheduler is 10msec too, so you can easily lose 10msec anywhere else no matter of whatever scheduler latency of 10msec. [...]
I agree with generally everything you say.
I think, however, you are making two assumptions:
(a) xmms has a very large leeway in the timing of its execution
(b) the maximum time a process sits in kernel space is 10ms.
While I agree (a) is true, it may not be so in all scenerios. Furthermore, the specified leeway does not exist for all timing-critical tasks. Not all of these tasks are specialized real-time applications, either.
Most importantly, however, the maximum latency of the system is not 10ms. Even _with_ preemption, we have observed greater latencies (due to long held locks).
This is why I believe the a preemptible kernel benefits more than just real-time signal processing.
Robert Love
Quoted 10 lines · Robert Love
Quoted 8 lines · Andrea Arcangeli
[...]
I think the issue you raise is that dbench gets a 10msec more of cpu time and xmms starts running 10msec later than expected (because of the scheduler latency peak worst case of 10msec).But that doesn't matter. The scheduler isn't perfect anyways. The resolution of the scheduler is 10msec too, so you can easily lose 10msec anywhere else no matter of whatever scheduler latency of 10msec. [...]
Quoted 5 lines
I agree with generally everything you say.
I think, however, you are making two assumptions:
(a) xmms has a very large leeway in the timing of its execution
Yes.
Quoted 1 line
(b) the maximum time a process sits in kernel space is 10ms.
Actually a task can sit in the kernel for its whole life and still provide usec scheduler latencies (ksoftirqd)
Quoted 1 line
While I agree (a) is true, it may not be so in all scenerios.
Correct, of course if you run xmms on a 16mhz CPU it will dropout no matter of the size of the dma buffer. And you're right the slower the CPU is the strictier the scheduler latency requirements to avoid the dropouts are. If the CPU is very slow as soon as xmms gets runnable it may not have enough time to decode the next mp3 data before the DMA ring drys out.
So yes I'm assuming doing playback on any recent cpu where xmms just hurts because it generates high frequency reschedule that in turns means tlb flushing on x86 (not because of the real cpu load). And mostly because of its "moving" GUI, not even because of the sound backend :).
Quoted 7 lines
Furthermore, the specified leeway does not exist for all timing-critical tasks. Not all of these tasks are specialized real-time applications, either.
Most importantly, however, the maximum latency of the system is not 10ms. Even _with_ preemption, we have observed greater latencies (due to long held locks).
I was reading a very detailed latency analyse done on the 2.4.10 SuSE kernel by Takashi and it showed 10msec peaks of worst case latency.
The stress during the latency measurement were x11perf (but ok, that's mostly userspace), /proc with top, disk write, disk read and disk copy.
But of course in -aa as said there's just the most important part of the low latency patch included, so without -aa I know for sure that the scheduler latency can run up to several seconds with lots of ram in the system (this is why I included only those scheduler points even in 2.2 for the multigigabyte machines, where the lack of rescheduling in read/write could become a patological case visible with eyes while typing in the shell).
And of course if you only apply the preempt patch and you don't add the explicit points in the cpu hogs under locks, you'll cover only copy-user lock less and semaphore parts, but not the other bits like the ones in the memory management that are also covered since 2.4.1[01] and in recent 2.2.
Quoted 2 lines
This is why I believe the a preemptible kernel benefits more than just real-time signal processing.
Provided that read/write gets fixed like in either Andrew's patch, Ingo's patch or -aa, I believe it cannot make any visible difference for mp3 playback in any recent machine. Feel free to experiment yourself with 2.4.11aa1.
Andrea
Quoted 2 lines · safemode
Heavily io bound processes (dbench 32) still causes something as light as an
mp3 player to skip, though. That probably wont be fixed intil 2.5, since
What buffer size are you using in your mp3 player? I have xmms set to 5000ms or so and it never skips. mpg321(esd or oss) also never skips no matter what I do, but the original mpg123-oss will with even light load on the cpu/disk.
This is with 2.4.10-ac9+preempt on an athlon 700
-Justin
Buffers, dbench and latency
In reply to safemodeI merge two comment... since they are related!
Quoted 3 lines · Andrea Arcangeli
Of course if xmms runs after the soundcard dma ring dried out, then there will be a dropout, but it would need seconds of scheduler latency to generate such a dropout which isn't going to happen.
Quoted 5 lines · Justin A
Quoted 3 lines · safemode
Heavily io bound processes (dbench 32) still causes something as light
as an mp3 player to skip, though. That probably wont be fixed intil
2.5, since
Quoted 7 lines
What buffer size are you using in your mp3 player? I have xmms set to 5000ms or so and it never skips. mpg321(esd or oss) also never skips no matter what I do, but the original mpg123-oss will with even light load on the cpu/disk.
This is with 2.4.10-ac9+preempt on an athlon 700
5000 ms == 5 s of buffered audio, assume 44100 k samples/s of 16 bit and 2 channels (5 channels is not that unusual) this gives a buffer of 882 kB ! or 215 pages! (Justin could probably fill in the actual details, but it does not really matter for the discussion below)
I do not think this is the size of the DMA ring buffer...
This is what I think is the situation, I have not read the xmms source - it could be implemented by one non blocking thread, but the analysis holds anyway (IMHO):
* One thread reads from disk to a xmms ring buffer of 5000 ms, this will give that tread lots of time to try to keep it big enough.
* Another thread, reads from this buffer, and writes to the DMA ring buffer. (usually fragmented in several parts)
When it gets full - this tread goes to sleep...
In this situation we could have two causes for dropouts.
* The second thread is really a RT tread. It gets woken up when one fragment has been used by the Audio DMA, i.e. new data can be written (often it got blocked in the write, and thus only needs to get the CPU for a brief moment). But it has to react in time...
Checking the source for emu10k1:
default fragment length is 20 ms, total default bufflen is 500 ms but, maximum buff size is 65536 Bytes = 16 pages
this gives a DMA buffer time in our example (44100 16 bit, stereo)
of: 370 ms
So this process has an absolute RT limit of 370 ms, not seconds!
+ this is the part were different low latency approaches work, since you might stay in kernel for longer times than this, there are loops over page descriptors where used data might not be in cache... The 10 ms figure claimed for 2.4.10 is not the whole truth...
+ The process buffer needs to be locked in memory, as all code that needs to execute to read from it and write to DMA buffer. Since a 5 s buffer will be written, and then staying idle for 5 s, before it is used (read) the next time...
* The same for the other process - it has more time to spare, but it has to keep the process buffer with data. And it is usually some sort of CPU hog - decoding compressed audio streams. It has to get scheduled in and allowed to run.
Note: dbench threads as most IO limited ones behaves nice from a
scheduler viewpoint - mostly waiting on IO resources. On my computer they use less CPU (0.3 % each) than artsd (10.8% and 1.1%) and noatune (1.9%). And that is not strange in any way since the audio processes actually has to do some calculations...
Now the scheduler has to choose - a process mostly waiting on IO or one that actually uses a part of its time slice...
If you are not running with lower nicelevel or SCHED_FIFO/RT to guarantee that you will be selected on next rescheduling - you will be in trouble...
/RogerL
Signature · 3 lines
Roger Larsson Skellefteå Sweden
Hi!
Quoted 4 lines
Now dbench (or any task) is in kernel space for too long. The CPU time xmms needs will of course still be given, but
_toolate_. Its just not a cpu resource problem, its a timing problem. xmms needs x units of CPU every y units of time. Just getting the x whenever is not enough.
Yep, with
x = 60msec
y = 600msec
So you can give it time up to 540msec late with no drop-outs.
Signature · 2 lines
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
Quoted 11 lines · Pavel Machek
Hi!
Quoted 4 lines
Now dbench (or any task) is in kernel space for too long. The CPU time xmms needs will of course still be given, but
_toolate_. Its just not a cpu resource problem, its a timing problem. xmms needs x units of CPU every y units of time. Just getting the x whenever is not enough.Yep, with
x = 60msec
y = 600msec
How are you arriving at that y? On what system?
I agree with the x value, though. However, people have been shouting a lot of numbers around about the size of audio buffers, the size of DMA buffers, etc. and they aren't realistic. If you calculate out the times that have been quoted, keeping in mind the stereo and all, the buffers are huge. We need to find out what the sizes _really_ are, and then keep in mind that we have multiple channels (plus any other sound output from X and what not).
Honestly, I don't know what the buffer sizes are. I do know audio skips for me, and preempt-kernel patch improves that.
Robert Love
Quoted 7 lines · Pavel Machek
Hi!
Quoted 4 lines
Now dbench (or any task) is in kernel space for too long. The CPU time xmms needs will of course still be given, but
_toolate_. Its just not a cpu resource problem, its a timing problem. xmms needs x units of CPU every y units of time. Just getting the x whenever is not enough.
Quoted 7 lines
Yep, with
x = 60msec
y = 600msecSo you can give it time up to 540msec late with no drop-outs.
How fast was the processor/memory on the system that produced these numbers?
Hi!
Quoted 11 lines
Quoted 9 lines
Quoted 4 lines
Now dbench (or any task) is in kernel space for too long. The CPU time xmms needs will of course still be given, but
_toolate_. Its just not a cpu resource problem, its a timing problem. xmms needs x units of CPU every y units of time. Just getting the x whenever is not enough.Yep, with
x = 60msec
y = 600msecHow are you arriving at that y? On what system?
Toshiba sattelite notebook. I remember being able to ^Z splay process playing mp3, and bg-ing it in time not to skip. That means that y is at least 300msec or so.
[I wanted to retry it on k6/400 with sblive and mpg123 (not splay) and could not do the trick.]
Pavel
Signature · 2 lines
Casualities in World Trade Center: 6453 dead inside the building, cryptography in U.S.A. and free speech in Czech Republic.