By the time you get to the socket, it might be eons (relatively
speaking) later, decreasing the usefulness of the timestamp.
As just an odd example if the TCP socket is user locked at the moment,
because the user is blocked on a GFP_KERNEL allocation, it could be
a very long time before we actually process the packet and timestamp
it.
UDP now does similar socket locking so could potentially hit the same
kind of problem.
That was my argument against such a change.
I find it amusing that nobody it talking about fixing the tools
that are creating the timestamp requests when they have no real
reason for having them in the first place.
--
