From: Jan Kiszka <jan.kiszka@domain.hid>
To: roland Tollenaar <rolandtollenaar@domain.hid>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] Latencies due to RT-Socket-CAN register accesses
Date: Tue, 24 Apr 2007 14:32:13 +0200 [thread overview]
Message-ID: <462DF8CD.6090304@domain.hid> (raw)
In-Reply-To: <bc4264770704240514i4478b0a4p890540bee5da8d8b@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
roland Tollenaar wrote:
>> > I am aware of this. For the current machine I will stick to this.
>> >
>>
>> Then don't complain. :)
> Yes sir!
> :)
> Not complaining really, I think and I hope that the latency of 30us
> average will do nicely for me. Just curious actually.
>
>> > to be give worse latencies than much slower machines. Are the 2
>> > interrupts causing the latency?
>>
>> Those two increase the latency of code in timed tasks, for sure. The
>> question is if your measurement on the slower machine also included this
>> scenario (timer event + 2 IRQs in a row). This definitely doesn't happen
>> often, and maybe timing on the slower box makes it less likely. Or there
>> is one potential IRQ source more on your fast box (e.g. due to IRQ
>> sharing on the slower one).
>>
>> You see, RT system design on the edge (ie. when hunting a few 10 us) is
>> tricky and not easily portable from box X to box Y.
>
> Its not possible to determine which IRQ's are responsible for this
> from the trace I presume?
>
echo 1 > /proc/ipipe/trace/verbose
Then look at the "User Val." reported at "common_interrupt" (see also [1]).
Jan
[1] http://www.xenomai.org/index.php/I-pipe:Tracer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-04-24 12:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 10:52 [Xenomai-help] Latencies due to RT-Socket-CAN register accesses Wolfgang Grandegger
2007-03-13 13:16 ` [Xenomai-help] " Roland Tollenaar
2007-03-13 13:29 ` Wolfgang Grandegger
2007-03-13 13:41 ` Roland Tollenaar
2007-03-13 14:06 ` Wolfgang Grandegger
2007-03-14 9:33 ` Wolfgang Grandegger
2007-03-28 17:05 ` roland Tollenaar
2007-03-28 18:50 ` Wolfgang Grandegger
2007-03-29 2:17 ` Roland Tollenaar
2007-03-29 8:38 ` Stéphane ANCELOT
2007-03-29 8:59 ` Wolfgang Grandegger
2007-03-29 16:44 ` Roland Tollenaar
2007-03-29 18:51 ` Gilles Chanteperdrix
2007-03-29 18:59 ` Wolfgang Grandegger
2007-04-23 15:09 ` [Xenomai-help] " roland Tollenaar
2007-04-23 18:28 ` Gilles Chanteperdrix
2007-04-24 8:44 ` roland Tollenaar
2007-04-24 8:56 ` Gilles Chanteperdrix
2007-04-24 10:27 ` roland Tollenaar
2007-04-24 10:27 ` roland Tollenaar
2007-04-24 12:57 ` Gilles Chanteperdrix
2007-04-24 18:36 ` roland Tollenaar
2007-04-24 9:05 ` Jan Kiszka
2007-04-24 10:31 ` roland Tollenaar
2007-04-24 10:51 ` Jan Kiszka
2007-04-24 12:14 ` roland Tollenaar
2007-04-24 12:32 ` Jan Kiszka [this message]
2007-04-24 10:57 ` Wolfgang Grandegger
2007-04-24 11:00 ` Jan Kiszka
2007-04-24 12:17 ` roland Tollenaar
2007-04-24 12:19 ` roland Tollenaar
2007-04-24 12:44 ` Wolfgang Grandegger
2007-04-25 9:04 ` Stéphane ANCELOT
2007-04-25 11:02 ` Roland Tollenaar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462DF8CD.6090304@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-help@domain.hid \
--cc=rolandtollenaar@domain.hid \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.