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:	Mon, 14 Jul 2008 21:30:12 +0300
From:	Octavian Purdila <>
To:	Oliver Hartkopp <>
Cc:	Andi Kleen <>,
Subject: Re: [rfc] new sk_buff member: hwstamp

> However i feel, that *one* nanosec resolution timestamp (as it already
> exists inside the skbuff) is enough. AFAIK the timestamp is only set in
> the netif_rx(), when it is not already set by the driver itself. For
> that reason i would suggest to create some semi-intelligent offset
> calculation inside the driver that makes the skb->tstamp value
> correspond with the hw timestamp and therefore transports the high
> resolution timestamp requirement into the userspace.

You mean something like here [1] ?

The problem for this approach in our usecase (one way delay measurement) is 
that the real time clock of the CPUs (of the RX and TX ports) is not 
synchronized, but the hw timestamp (implemented in the NIC/FPGA) is. 



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