Hello linux-rt-users,
I have a question concerning RT-Patch, which shows strange behavior
discoverd using cyclictest. I have an embedded system with patched RT.
The max latency of the cyclictest isn’t as low as expected and my only
application hangs to, so I included tracing abilities to the kernel to
use the “-b” switch of cyclictest. But the kernel behaves different if
switched on (detailed below)? Maybe you can give me a hint what the
cyclictest does when using the –b switch. It somehow persists after the
option is used once and my own application runs fine afterwards too. So
in order to run my application right now I have to run cyclictest with
the -b option after each reboot.
Many Thanks in Advance
Paul Ehrlich
First test run after boot - showing huge latencies:
linaro@linaro-ubuntu-desktop:~$ sudo cyclictest -t1 -p 80 -n -i 250 -l
10000 -a 1
# /dev/cpu_dma_latency set to 0us
policy: fifo: loadavg: 0.74 0.34 0.13 1/144 1966
T: 0 ( 1966) P:80 I:250 C: 10000 Min: 18 Act: 27 Avg: 36 Max: 1590
Secound test run after boot - just to make sure:
linaro@linaro-ubuntu-desktop:~$ sudo cyclictest -t1 -p 80 -n -i 250 -l
10000 -a 1
# /dev/cpu_dma_latency set to 0us
policy: fifo: loadavg: 0.93 0.30 0.10 1/142 1948
T: 0 ( 1948) P:80 I:250 C: 10000 Min: 18 Act: 46 Avg: 38 Max: 3639
Third test run after boot now using -b option - result looks ok for the
system:
linaro@linaro-ubuntu-desktop:~$ sudo cyclictest -t1 -p 80 -n -i 250 -l
10000 -a 1 -b 1000
# /dev/cpu_dma_latency set to 0us
INFO: debugfs mountpoint: /sys/kernel/debug/tracing/
policy: fifo: loadavg: 0.51 0.32 0.13 1/144 1979
T: 0 ( 1979) P:80 I:250 C: 10000 Min: 85 Act: 101 Avg: 114 Max: 179
Fourth run after boot - now without -b even faster?:
# Thread Ids: 01979
linaro@linaro-ubuntu-desktop:~$ sudo cyclictest -t1 -p 80 -n -i 250 -l
10000 -a 1
# /dev/cpu_dma_latency set to 0us
policy: fifo: loadavg: 0.66 0.38 0.16 1/157 2283
T: 0 ( 2279) P:80 I:250 C: 10000 Min: 6 Act: 27 Avg: 27 Max: 51
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
