From: Jan Kiszka <jan.kiszka@domain.hid>
To: Benjamin Biegel <biegel@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] What has highest priority RTcap or TDMA-synchronization reception?
Date: Sat, 14 Nov 2009 12:12:40 +0100 [thread overview]
Message-ID: <4AFE90A8.7090403@domain.hid> (raw)
In-Reply-To: <4AFD6013.9020608@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]
Benjamin Biegel wrote:
> Thanks Jan
>
> We use this setup: Two computers are RTnet-slaves synchronized to provide them common time. These two computers also have a second NIC which tap a target Ethernet network using RTcap. In this way we can measure Ethernet travel times on the target network.
>
> This works well. The only problem is that we don't know exactly how to handle if a TDMA sync arrives at the same time as RTcap captures a frame on the target network.
>
> We ran a test where we only read the system time from kernel space using rt_timer_read(). This reading and saving to a file takes approximately 1 us. However this time increases to approx 16 us when the reading is made when a synchronization TDMA packet is being handled.
>
> We would like to detect when this happens so we can discard the frame travel times that collide with the TDMA sync.
>
> I hope this makes sense
Note that the synchronization accuracy via TDMA is not in the order of a
few microseconds, rather a few 10 us. That's because no clever approach
to compensate jitters of the reception interrupt is applied. So your
worrying about the jitter caused by the second NIC actually has to be
extended by worries about jitter of other host interrupts. They might be
smaller as I-pipe will suppress non-RT IRQs far more quickly, but they
are more and can line up and cause larger jitters as well.
If you want to get rid of most of them: use a multicore box and isolate
the RTnet NIC IRQ on a dedicated core. All Linux IRQs except for the
timer IRQ can then be avoided.
And I still see no point in using a second NIC if the first one is only
_receiving_ TDMA sync frames. It's true that timestamps taken by RTcap
on outgoing frames will naturally slightly differ from those taken by a
listen-only observer - but to my understanding this scenarios does not
apply to you case. So RTcap will work just fine when attached already to
the first NIC.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-11-14 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 6:50 [Xenomai-help] What has highest priority RTcap or TDMA-synchronization reception? Benjamin Biegel
2009-11-13 12:09 ` Jan Kiszka
2009-11-13 13:33 ` Benjamin Biegel
2009-11-14 11:12 ` Jan Kiszka [this message]
2009-11-14 11:17 ` Jan Kiszka
2009-11-19 15:07 ` [Xenomai-help] How to capture frames with RTcap without TDMA? Benjamin Biegel
2009-11-20 10:45 ` [Xenomai-help] Solved - " Benjamin Biegel
2009-11-24 16:19 ` [Xenomai-help] What has highest priority RTcap or TDMA-synchronization reception? Benjamin Biegel
2009-11-24 23:06 ` Jan Kiszka
2009-11-14 22:59 ` Benjamin Biegel
2009-11-15 16:24 ` Jan Kiszka
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=4AFE90A8.7090403@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=biegel@domain.hid \
--cc=xenomai@xenomai.org \
/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.