netdev - time stamping packets (on Rx side)

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-next>] [day] [month] [year] [list]

Message-ID: <CAAsGZS4OvqyRr-1vvTzW5+Lx5007tuwP5GsZHRDXEOY4q1Mw1A@mail.gmail.com>
Date:	Thu, 15 Mar 2012 14:13:01 -0400
From:	chetan loke <loke.chetan@...il.com>
To:	netdev <netdev@...r.kernel.org>
Subject: time stamping packets (on Rx side)

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.

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