Re: [Y2038] [PATCH] aoe: Use 64-bit timestamp in frame

2015-05-13 Thread Ed Cashin
On 05/13/2015 04:04 AM, Arnd Bergmann wrote: ... Shall we do the ktime_get_us() approach then? It still requires a 32-bit division like do_gettimeofday(), so it will not be as efficient as the shifted nanoseconds. It's no worse, though, right? So I think it's a good transition. Further optimi

Re: [Y2038] [PATCH] aoe: Use 64-bit timestamp in frame

2015-05-13 Thread Arnd Bergmann
On Tuesday 12 May 2015 21:23:04 Ed Cashin wrote: > On 05/12/2015 07:14 AM, Arnd Bergmann wrote: > > On Tuesday 12 May 2015 11:44:21 Arnd Bergmann wrote: > >> There are of course multiple ways to do this. One way would be to > >> change the code to work on 32-bit nanoseconds instead of 32-bit > >> m

Re: [Y2038] [PATCH] aoe: Use 64-bit timestamp in frame

2015-05-12 Thread Ed Cashin
On 05/12/2015 07:14 AM, Arnd Bergmann wrote: On Tuesday 12 May 2015 11:44:21 Arnd Bergmann wrote: There are of course multiple ways to do this. One way would be to change the code to work on 32-bit nanoseconds instead of 32-bit microseconds. This requires proving that the we cannot exceed 4.29 s

Re: [Y2038] [PATCH] aoe: Use 64-bit timestamp in frame

2015-05-12 Thread Arnd Bergmann
On Tuesday 12 May 2015 11:44:21 Arnd Bergmann wrote: > > There are of course multiple ways to do this. One way would be to > change the code to work on 32-bit nanoseconds instead of 32-bit > microseconds. This requires proving that the we cannot exceed > 4.29 seconds of round-trip time in calc_rtt