[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4oucHWL=DLwkZo2CUjNSK+P77Bh2i-uBeRbP8m3QBY4qj0w@mail.gmail.com>
Date: Thu, 23 Feb 2023 14:08:00 +0100
From: Íñigo Huguet <ihuguet@...hat.com>
To: Richard Cochran <richardcochran@...il.com>
Cc: Vadim Fedorenko <vadim.fedorenko@...ux.dev>,
ecree.xilinx@...il.com, habetsm.xilinx@...il.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, netdev@...r.kernel.org,
Yalin Li <yalli@...hat.com>
Subject: Re: [PATCH net-next v4 3/4] sfc: support unicast PTP
On Wed, Feb 22, 2023 at 5:52 PM Richard Cochran
<richardcochran@...il.com> wrote:
>
> On Wed, Feb 22, 2023 at 03:41:51PM +0100, Íñigo Huguet wrote:
>
> > The reason is explained in a comment in efx_ptp_insert_multicast filters:
> > Must filter on both event and general ports to ensure
> > that there is no packet re-ordering
>
> There is nothing wrong with re-ordering. Nothing guarantees that
> datagrams are received in the order they are sent.
>
> The user space PTP stack must be handle out of order messages correct
> (which ptp4l does do BTW).
That's good to know, thanks.
Anyway,this patch set addresses the addition of Unicast PTP support,
and regarding the timestamping of PTP-general packets it has
maintained the existing driver behaviour. So I hope this is not a
blocker for the current patches, I think it should be addressed in a
different patch set if the time permits.
>
> Thanks,
> Richard
>
--
Íñigo Huguet
Powered by blists - more mailing lists