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  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]
Date:	Fri, 16 Mar 2012 08:10:39 +0100
From:	Richard Cochran <>
To:	chetan loke <>
Cc:	netdev <>
Subject: Re: time stamping packets (on Rx side)

On Thu, Mar 15, 2012 at 02:13:01PM -0400, chetan loke wrote:
> Hello,
> So with the (ptp clock support)PHC in place, some apps can use it as a
> reference clock. But if I'm trying to debug/analyze packets(by TAP'ing
> a link) using linux then I might still have a problem. Does Intel (or
> any adapter with 1588 support) have the capability to time stamp the
> packet on the NIC and not on the host side?  Because if we time stamp
> on the host side then it all depends when we drain Port0 and Port1's
> Rx descriptors of the dual-port NIC. It's quite possible that we might
> see reply before request. But if the pkt was stamped by the NIC then
> we know for sure which came first.

Not sure what you mean by NIC/host side.

But, yes, time stamping every received packet in the MAC is a nice
feature. Be careful when choosing your hardware, since many cards with
PTP hardware time stamping *only* stamp the PTP packets.

Some cards can provide a time stamp in the frame or in its control
block, and thus time stamp every packet. The Intel 82580 can do this,
and so can the Freescale gianfar controller (well, some of them,


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists