netdev - Re: [RFC 0/4] net: enable timestamps on a per-socket basis

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 Apr 2008 00:28:45 -0700
From:	Jason Uhlenkott <juhlenko@...mai.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, shemminger@...ux-foundation.org
Subject: Re: [RFC 0/4] net: enable timestamps on a per-socket basis

On Sun, Apr 20, 2008 at 23:03:56 -0700, David Miller wrote:
> Moving the timestamp up to a higher level takes away some of the
> frequent use cases of timestamps, which is to detect things like the
> fact that it is taking a long time for packets to get from the
> top-level packet receive down to the actual protocol processing.
> 
> With your patch, it can't be used that way any more.
> 
> In fact, people are desiring timestamps which are _closer_ to when the
> device actually receives the frame rather than further away.

Fair enough.

It's too bad that SO_TIMESTAMP has a scope of impact which really has
nothing to do with a socket, though.  It almost seems like it should
have been an interface flag instead of a socket option.
--
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