[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d51dce20-5365-5653-d5af-972132bc40ac@gmail.com>
Date: Mon, 3 Apr 2023 14:13:13 +0100
From: Edward Cree <ecree.xilinx@...il.com>
To: Íñigo Huguet <ihuguet@...hat.com>,
habetsm.xilinx@...il.com
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, richardcochran@...il.com,
netdev@...r.kernel.org, Yalin Li <yalli@...hat.com>
Subject: Re: [PATCH v6 net-next 0/4] sfc: support unicast PTP
On 31/03/2023 12:14, Íñigo Huguet wrote:
> Unicast PTP was not working with sfc NICs.
>
> The reason was that these NICs don't timestamp all incoming packets,
> but instead they only timestamp packets of the queues that are selected
> for that. Currently, only one RX queue is configured for timestamp: the
> RX queue of the PTP channel. The packets that are put in the PTP RX
> queue are selected according to firmware filters configured from the
> driver.
>
> Multicast PTP was already working because the needed filters are known
> in advance, so they're inserted when PTP is enabled. This patches
> add the ability to dynamically add filters for unicast addresses,
> extracted from the TX PTP-event packets.
>
> Since we don't know in advance how many filters we'll need, some info
> about the filters need to be saved. This will allow to check if a filter
> already exists or if a filter is too old and should be removed.
>
> Note that the previous point is unnecessary for multicast filters, but
> I've opted to change how they're handled to match the new unicast's
> filters to avoid having duplicate insert/remove_filters functions,
> once for each type of filter.
>
> Tested: With ptp4l, all combinations of IPv4/IPv6, master/slave and
> unicast/multicast
>
> Reported-by: Yalin Li <yalli@...hat.com>
> Signed-off-by: Íñigo Huguet <ihuguet@...hat.com>
Reviewed-by: Edward Cree <ecree.xilinx@...il.com>
Powered by blists - more mailing lists