Re: CONFIG_PREEMPT and server workloads

From: Takashi Iwai
Date: Wed Mar 24 2004 - 08:58:49 EST

At Sat, 20 Mar 2004 16:03:11 +0100,
Andrea Arcangeli wrote:
> On Sat, Mar 20, 2004 at 06:51:11AM -0800, William Lee Irwin III wrote:
> > I may have missed one of his posts where he gave the results from the
> > RT test suite. I found a list of functions with some kind of numbers,
> > though I didn't see a description of what those numbers were and was
> > looking for something more detailed (e.g. the output of the RT
> > instrumentation things he had with and without preempt). This is all
> > mostly curiosity and sort of hoping this gets carried out vaguely
> > scientifically anyway, so I'm not really arguing one way or the other.
> agreed. what I've seen so far is a great number of graphs, they were
> scientific enough for my needs and covering real life different
> workloads, but I'm not sure what Takashi published exactly, you may want
> to discuss it with him.

sorry, there is no exact descrption (yet) in public, except for the
pdf of slides i presented ago:

the data there are already old (based on 2.6.0-test9), and were
measured by the old version of latency-test program (modifed version
from Benno Senor's latencytest suite).

basically, the latency-test program measures the latency between the
time of (periodical) irq and the time when user RT-thread is woken
up under different workloads. the user thread can perform an
artificial CPU load (busy loop) to simulate the situation that any RT
process does a heavy job.

the resultant plot shows the critical deadline, the total latency and
the CPU latency (busy loop) responses, as you can see in the above

the latest version of latency-test suite is found at

it uses its own kernel module to generate irqs from RTC and to trace

i'll show the results of the recent kernels tomorrow...

Takashi Iwai <tiwai@xxxxxxx> ALSA Developer -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at