>Posted by Gilles Chanteperdrix on January 27, 2011 - 14:36:

>Strange, here, the LTP test takes only around 2 hours. Just to be sure:
>you also generated disk and network activity in parallel to LTP and
>latency? If yes, then this system has no issue with Xenomai, and the
>problem you have with your application is in the application itself.

I launch runltp command with -t flag (which specifies test duration) to run LTP tests for one day.
I cannot run nettests and disk I/O tests from ltp battery because they require additional features (former requires another linux PC with ltp installed, latter requires floppy and CD player which aren't present
on my pc).
So, I create a script that downloads via network a larger (100Mb) file, and create, copy and delete some files on hard disk, all in a while loop, to generate network and disk I/O traffic.
I re-run ltp and latency test running for 15 hours in parallel with this script also.
I obtain:

RTD| 1.081| 8.000| 47.249| 0| 0| 14:58:34/14:58:34

Now I can assert that my xenomai works grat, I think.
And then, problems are in my application.

The only thing that looks me strange is this: with ltp+my_I/O_stress_script+latency tests, I obtain a minimum latency value (1.081) that is more less than ltp+latency only tests (6.182).
So, lower latency was obtained with higher system load.
Maybe there's some CPU frequency reductions in act during ltp+latency that isn't active during ltp+latency+my_I/O_stress_script, also if in my kernel configuration CPU frequency stepping was disabled?
Or what could be happened?

Thank you very much for your helpfullness, Gilles.