Thank you, Gilles
1) Yeah, I understand that my application (originally written for VxWorks) is not adapted somehow to work properly under Xenomai (the threads are switching to secondary mode very often, for example)..ok..but, test application is also running under xenomai and if I define the highest priority for my test task it should show the best latency it can ever get from Xenomai, I'm I right?
Could you please comment what kind of BUG I should try find out...in how should I optimize my application?
2) which options you usualy use for diff command to make the proper (I mean the format which is commonly used by Xenomai guys) diff file?
3) Do you have enough documentation where I can find the answers for my questions?
Looks like yes, since you ignore answering the questions I asked you. Give me the links on it then, please!
Thank you,
Sergey
On 11 February 2010 20:43, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
Sergey Didenko wrote:
> Hello
>
> As a unit:
> 1) Board MV88F6290
> 2) Linux Kernel 2.6.29
> 3) Xenomai version 2.5.1
>
> I have new latency test results for Xenomai 2.5.1!
>
> I adjusted /proc/xenomai/latency value for kernel mode from 9503 to 5099
> (making minimum latency more close to 0)
> And there is a big difference (in comparission with xenomai 2.4.9 version)
> in case of user-mode, with xenomai 2.4.9, adjusted value was 4400, but with
> xenomai 2.5.1 I have to set it to 44300 (! 10 times bigger) to get the
> minimum latency very close to 0.
> All test for user mode I did with value /proc/xenomai/latency = 0
> All test for kernel mode I did with value /proc/xenomai/latency = 5100
I can confirm that Xenomai is working well on other ARM platforms. So,
this issue is specific to your platform. Look for the bug in your code.
--
Gilles.