On Sun, 23 Dec 2001, Victor Yodaiken wrote:
>
>
> Run a "RT" task that is scheduled every millisecond (or time of your
> choice)
> while(1`){
> read cycle timer
> clock_nanosleep(time period using aabsolute time
> read cycle timer - what was actual delay? track worst
> case
> }
>
> Run this
> a) on aaaaaaaaan unstressed system
> b) under stress
> c) while a timed non-rt benchmark runs to figure out "RT"
> overhead.
I've coded a test app that uses the LatSched latency patch ( that uses
rdtsc ).
It basically does 1) set the current process priority to RT 2) an ioctl()
to activate the scheduler latency sampler 3) sleep for 1-2 secs 4) ioctl()
to stop the sampler 5) peek the sample with pid == getpid().
In this way i get the net RT task scheduler latency. Yes it does not get
the real one that includes accessories kernel paths but my code does not
affect these ones. And they add noise to the measure.
- Davide
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:31 EST