netdev - SO_TIMESTAMP on tcp sockets?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 May 2012 18:39:48 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Network Development <netdev@...r.kernel.org>
Subject: SO_TIMESTAMP on tcp sockets?

I've been using SO_TIMESTAMPNS to good effect on udp sockets.  I'd
like to do the same thing for tcp.  I realize that this is
semantically strange [1], but I don't think there's a real issue for
my use case.  We have very thin streams -- we are likely to process
each incoming segment as it is received, and I want the most precise
timestamp possible on each segment.

A simple approach (I think) would be for a recvmsg on a tcp socket
with SO_TIMESTAMP(NS) to return at most one skb worth of data along
with the timestamp associated with that skb.  This could be a little
strange if multiple segments overlap or if lro is involved, but
neither of those cases seems like a major problem.

Is there any interest in something like this?

Thanks,
Andy

[1] http://comments.gmane.org/gmane.linux.network/159574
--
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