----- "David Miller" <davem@davemloft.net> wrote:
quoted text
> 
> Every application using AF_PACKET sockets gets timestamps by
> default.  And we do know of several specific cases where the
> timestamps are unnecessary.
> 
> Even for other cases, why in the world does a DHCP client need
> accurate timestamps?  Give me a break. :)
> 

I've worked with systems where SO_TIMESTAMP has been used for
H.323 videoconferencing systems to synchronize audio and video
where remote systems' timestamps on the protocol streams proved
to be inaccurate (based off of different, unsynchronized clocks).

I can't see any other realistic use of this, but trying to get
timestamps for quasi-realtime protocols may be an important use
case - and in that case, you want the time when it hits the
interface, NOT when it hits the socket.

What utility does the time of hitting the socket get you?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html