From: Octavian Purdila <opurdila@ixiacom.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Subject: Re: [RFC] support for IEEE 1588
Date: Fri, 4 Jul 2008 03:42:36 +0300 [thread overview]
Message-ID: <200807040342.36505.opurdila@ixiacom.com> (raw)
In-Reply-To: <486D6B87.9030409@hp.com>
On Friday 04 July 2008, Rick Jones wrote:
> I've not had a good emily litella moment in at least a week, so I'll ask
> - if the clock in the hardware generating the timestamp and the clock in
> the host aren't synchronized in _some_ way, what benefit is there to
> putting the hardware's timestamp in there?
>
We actually currently use them for delay/jitter calculation in conjunction
with having the RX and TX port's source timestamping units running in sync.
We can do that since both the RX and TX port (Linux based) will run in our
hardware (chassis).
I guess we could try to do a simple sync between the host clock and the hw
clock by getting the initial delta between the two. But since the two clocks
are not in sync, they will diverge in time. And since I do not know enough
about the way in which tstamp is currently used, I'm not very confident that
this will not break something... so, back to grepping :)
Thanks,
tavi
next prev parent reply other threads:[~2008-07-04 0:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 22:47 [RFC] support for IEEE 1588 Octavian Purdila
2008-07-03 23:24 ` Stephen Hemminger
2008-07-03 23:40 ` Octavian Purdila
2008-07-04 0:15 ` Rick Jones
2008-07-04 0:42 ` Octavian Purdila [this message]
2008-07-04 11:24 ` Andi Kleen
2008-07-04 13:37 ` Patrick Ohly
2008-07-05 0:21 ` Octavian Purdila
2008-07-07 12:34 ` Patrick Ohly
2008-07-09 15:31 ` Lennart Sorensen
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=200807040342.36505.opurdila@ixiacom.com \
--to=opurdila@ixiacom.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=shemminger@vyatta.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).