On 10/9/07, Gregory CLEMENT <[EMAIL PROTECTED]> wrote:
> 2007/10/9, Gilles Chanteperdrix <[EMAIL PROTECTED]>:
> > You had latencies smaller than 100us already in user-space. So, the
> > fact that you get higher latencies in kernel-space is highly
> > suspicious.
> Where do you see it is in user space ? The latency are colected in
> kernel module, it is just display wich is in user space.
No, the first and third test mentions clearly "periodic user-mode
task", which means that you launched the latency test with no -t
option or with -t 0, in this case, latencies are collected in
user-space. If you want to collect latencies in kernel space, you
should run latency with the -t 1 (kernel-space thread) or -t 2
(kernel-space timer handler) option.
> Then the 100us I mentionned are under calibrator load, which is the
> application which give the worse resulats. On the result yout point
> the max lantency is 200us.
Ok, I missed this one because I did not see the RTT header.
> We reached 100us by set dbgu priority to 6, and maintain timer
> priority to 7. Indeed serial output on dbu give bad latency as it its
> peripheral ID is 0, so with the same level of priority in AIC, its
> interrupt are treated first. We change this in adeos fot both RTAI and
> Maybe this change can be done in adeos main tree.
Well, that is interesting. But it would have been nice to tell us
about this, so that we could have fixed the I-pipe patch.
Xenomai-core mailing list