netdev - Re: [RFC][PATCH 0/2] net: support for TX timestamps

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]

Date:	Wed, 30 Jul 2008 16:02:08 +0300
From:	Octavian Purdila <opurdila@...acom.com>
To:	Ingo Oeser <netdev@...eo.de>
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC][PATCH 0/2] net: support for TX timestamps

On Wednesday 30 July 2008, Ingo Oeser wrote:

> > This patches adds TX timestamping support and is main use case is the
> > Precision Time Protocol (IEEE 1588). Both software and hardware
> > timestamping can be used.
>
> Could you please include an example on how to use
> this in userspace?
>
> A proper place for this would be Documentation/net/
>
> At the moment I cannot imagine how to use this and how
> to correlate the sent packet with the timestamp.
>
> That would also be a way to test your implementation and
> test any changes done later to it. This will avoid future bitrot.
>

Yes, of course. 

I am also planning to add mac/network/transport layer pointers in the 
sock_extended_err, so that the application can easily "navigate"  the packet 
in the error queue and map it to the sent packet. 

Thanks for the input!

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