Re: [rfc] new sk_buff member: hwstamp

[Octavian Purdila <opurdila@ixiacom.com>]

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

[1] 
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc4/2.6.23-rc4-mm1/broken-out/sky2-hardware-receive-timestamp-counter.patch

Thanks,
tavi