From: Stephen Hemminger <shemminger@vyatta.com>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] support for IEEE 1588
Date: Thu, 3 Jul 2008 16:24:28 -0700 [thread overview]
Message-ID: <20080703162428.55d9f345@extreme> (raw)
In-Reply-To: <200807040147.11148.opurdila@ixiacom.com>
On Fri, 4 Jul 2008 01:47:11 +0300
Octavian Purdila <opurdila@ixiacom.com> wrote:
>
> Hi everybody,
>
> IEEE 1588 Precision Time Protocol [1] requires hardware timestamping support
> for both RX and TX frames. It seems that in Linux we do not have the support
> required for this protocol to be implemented.
>
> Any feedback on the approach we are planing to take is greatly appreciated. We
> will follow with a patch at some point, but I just want to check with you
> gurus early, to avoid potential design flaws. If a patch is preferred for
> commenting on, then please ignore this and will come back later with the
> patch.
>
> 1. RX path
> - add a new field in skb to keep the hardware stamp (hwstamp)
> - add a new socket flag to enable RX stamping
> - add a new control message to retrieve the hwstamp from the skb to user-space
> application (for UDP and maybe PF_PACKET)
The existing skb timestamp is there, and if the hardware supports it, it could
be updated by the device driver I had a version of sky2 that did just that
but never fully pushed it upstream because of available time and testing issues.
The API's are already there (and used) for timestamping; don't invent
new ones.
next prev parent reply other threads:[~2008-07-03 23:24 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 [this message]
2008-07-03 23:40 ` Octavian Purdila
2008-07-04 0:15 ` Rick Jones
2008-07-04 0:42 ` Octavian Purdila
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=20080703162428.55d9f345@extreme \
--to=shemminger@vyatta.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.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).