netdev - Re: [RFC] support for IEEE 1588

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200807040240.04801.opurdila@ixiacom.com>
Date:	Fri, 4 Jul 2008 02:40:04 +0300
From:	Octavian Purdila <opurdila@...acom.com>
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC] support for IEEE 1588

On Friday 04 July 2008, Stephen Hemminger wrote:

> >
> > 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.

Hi Stephen,

Thanks for taking the time to respond.

The hardware we will be using will not have the timestamping unit synchronized 
to gettimeofday(). In this conditions, is it OK to put our hw stamp into 
skb->tstamp?

Also, are there any APIs we can use on the TX side as well?

Thanks,
tavi


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html