On Tue, 1 Oct 2019 at 13:50, Miroslav Lichvar <mlich...@redhat.com> wrote: > > On Tue, Oct 01, 2019 at 01:00:00PM +0300, Vladimir Oltean wrote: > > On Tue, 1 Oct 2019 at 12:22, Miroslav Lichvar <mlich...@redhat.com> wrote: > > > I think it's expected that two messages sent within few microseconds or > > > milliseconds can be received in a wrong order and PTP slaves need to > > > handle that. But it's not expected that a message will be delayed so > > > much that it will be received after a message that was sent one or > > > more sync intervals later. > > > > Not even if I'm testing with logSyncInterval -5? > > No, I'd not expect to receive a follow-up message 30 milliseconds > after the corresponding sync message. If the difference was getting to > the millisecond range, I'd be worried that the network is so > overloaded or misconfigured that it might drop some PTP messages. >
What about a sync interval of 2^-4, which is what is specified by the G.8275.1 telecom profile (supported by linuxptp as there is a config file for it)? What about the automotive profile which uses a sync interval of 2^-3 before arriving at the stable state? Where do you draw the line, and how do you deal with reordering in those profiles? > -- > Miroslav Lichvar Regards, -Vladimir _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
