Re: [PATCH v3 net-next 5/7] net: don't make false software transmit timestamps

2017-05-17 Thread Willem de Bruijn
On Wed, May 17, 2017 at 6:27 AM, Miroslav Lichvar wrote: > On Tue, May 16, 2017 at 06:34:38PM -0400, Willem de Bruijn wrote: >> On Tue, May 16, 2017 at 8:44 AM, Miroslav Lichvar >> wrote: >> > If software timestamping is enabled by the SO_TIMESTAMP(NS) option >> > when a message without timestam

Re: [PATCH v3 net-next 5/7] net: don't make false software transmit timestamps

2017-05-17 Thread Miroslav Lichvar
On Tue, May 16, 2017 at 06:34:38PM -0400, Willem de Bruijn wrote: > On Tue, May 16, 2017 at 8:44 AM, Miroslav Lichvar wrote: > > If software timestamping is enabled by the SO_TIMESTAMP(NS) option > > when a message without timestamp is already waiting in the queue, the > > __sock_recv_timestamp()

Re: [PATCH v3 net-next 5/7] net: don't make false software transmit timestamps

2017-05-16 Thread Willem de Bruijn
On Tue, May 16, 2017 at 8:44 AM, Miroslav Lichvar wrote: > If software timestamping is enabled by the SO_TIMESTAMP(NS) option > when a message without timestamp is already waiting in the queue, the > __sock_recv_timestamp() function will read the current time to make a > timestamp in order to alwa

[PATCH v3 net-next 5/7] net: don't make false software transmit timestamps

2017-05-16 Thread Miroslav Lichvar
If software timestamping is enabled by the SO_TIMESTAMP(NS) option when a message without timestamp is already waiting in the queue, the __sock_recv_timestamp() function will read the current time to make a timestamp in order to always have something for the application. However, this applies also