[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 6 Jun 2023 11:10:19 +0100
From: Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@....com>
To: edward.cree@....com, linux-net-drivers@....com, davem@...emloft.net,
kuba@...nel.org, pabeni@...hat.com, edumazet@...gle.com
Cc: Edward Cree <ecree.xilinx@...il.com>, netdev@...r.kernel.org,
habetsm.xilinx@...il.com
Subject: Re: [PATCH net-next 1/6] sfc: add fallback action-set-lists for TC
offload
On 05/06/2023 20:17, edward.cree@....com wrote:
> From: Edward Cree <ecree.xilinx@...il.com>
>
> When offloading a TC encap action, the action information for the
> hardware might not be "ready": if there's currently no neighbour entry
> available for the destination address, we can't construct the Ethernet
> header to prepend to the packet. In this case, we still offload the
> flow rule, but with its action-set-list ID pointing at a "fallback"
> action which simply delivers the packet to its default destination (as
> though no flow rule had matched), thus allowing software TC to handle
> it. Later, when we receive a neighbouring update that allows us to
> construct the encap header, the rule will become "ready" and we will
> update its action-set-list ID in hardware to point at the actual
> offloaded actions.
> This patch sets up these fallback ASLs, but does not yet use them.
>
> Signed-off-by: Edward Cree <ecree.xilinx@...il.com>
Reviewed-by: Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@....com>
Powered by blists - more mailing lists