> -----Original Message----- > From: Richard Cochran <richardcoch...@gmail.com> > Sent: Thursday, July 8, 2021 7:42 PM
> On Thu, Jul 08, 2021 at 01:10:08PM +0200, Miroslav Lichvar wrote: > > On Thu, Jul 08, 2021 at 01:37:38AM +0000, Eric Decker wrote: > > > If the timestamp is available in less than the timeout (5ms) will it > > > still wait > for the timeout, or continue processing after the timestamp is received? > > > > The poll() call is waiting for the descriptor, so it should return as > > soon as the timestamp is ready. The option sets the maximum time it > > waits. > > But on kernels older than (mumble) (3.5?) the code will sleep the entire > period, then wake to read the time stamp. > Can we reverse the thinking and define what's the maximum time we can allow the SW to poll for the timestamp? Can it be a half of the packet rate? Or there is any reason to make a specific tighter limit to it? Regards Maciek _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
