netdev - Re: CLOCK_MONOTONIC datagram timestamps by the kernel

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:	Thu, 1 Mar 2007 13:03:26 +0300
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	John <linux.kernel@...e.fr>
Cc:	Eric Dumazet <dada1@...mosbay.com>, linux-net@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: CLOCK_MONOTONIC datagram timestamps by the kernel

On Wed, Feb 28, 2007 at 05:07:10PM +0100, John (linux.kernel@...e.fr) wrote:
> Again, this is irrelevant. We are discussing whether it would make sense 
> to support sub-microsecond resolution. If there is one platform that can 
> achieve sub-microsecond precision, there is a need for sub-microsecond 
> resolution. As long as we are changing the resolution, we might as well 
> use something standard like struct timespec.

You can not blindly change skb timestamps to different entities - you
need to change all users (at least in kernel).
Exporting it to userspace must require new socket option and old one ust
be changed accordingly, but there is nothing wrong in having nanosecond
resolution in packet timestamp except that it might not be 100% correct
receiving time.

-- 
	Evgeniy Polyakov
-
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