From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai and Libpcap
Date: Thu, 22 Oct 2009 18:58:26 +0200 [thread overview]
Message-ID: <4AE08F32.80800@domain.hid> (raw)
In-Reply-To: <4AE086A0.1050703@domain.hid>
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> As far as I remember, however, the timestamping of each packet is done
>> in the Linux domain, so, if you want to get the real timestamp, you have
>> to modify rtnet to get the timestamp done in the Xenomai domain.
>
> No, time stamping is actually done in the RTnet driver (it is a
> by-product of RTmac/TDMA).
Ok, right, bad memory.
>
>> Unfortunately, that is not all, because if you get Xenomai's timestamp,
>> they drift when compared to Linux timestamps. But if you look only at
>> relative timestamps over short period of times, that is Ok.
>>
>
> Yes, timestamps will drift compared to a precise reference clock or even
> the Linux host clock. But I'm optimistic we can fix this in the neat future.
Ok. Now I remember why I touched this: in secondary domain, while
copying the packet for the rtcap driver, I read Xenomai's real-time
clock and Linux' real-time clock, and subtracted to Linux' timestamp the
difference between Xenomai's timestamp and the packet timestamp. This
compensates for the drift.
However, I far as I understood, Benjamin wants to get timestamps using
the NIC's clock. So, the solution would be a bit different.
--
Gilles
next prev parent reply other threads:[~2009-10-22 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 14:38 [Xenomai-help] Xenomai and Libpcap Fillod Stephane
2009-10-22 15:11 ` Gilles Chanteperdrix
2009-10-22 16:21 ` Jan Kiszka
2009-10-22 16:58 ` Gilles Chanteperdrix [this message]
2009-10-22 22:06 ` Benjamin Biegel
-- strict thread matches above, loose matches on Subject: below --
2009-10-22 12:39 Benjamin Biegel
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=4AE08F32.80800@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@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.