> -----Original Message-----
> From: Lorenzo Bianconi <lore...@kernel.org>
> Sent: Monday, March 8, 2021 13:07
> To: b...@vger.kernel.org
> Cc: netdev@vger.kernel.org; da...@davemloft.net; k...@kernel.org;
> a...@kernel.org; dan...@iogearbox.net; bro...@redhat.com;
> t...@redhat.com; freysteinn.alfreds...@kau.se;
> lorenzo.bianc...@redhat.com; john.fastab...@gmail.com;
> jasow...@redhat.com; m...@redhat.com; thomas.petazz...@bootlin.com;
> m...@semihalf.com; li...@armlinux.org.uk; ilias.apalodi...@linaro.org;
> neta...@amazon.com; akiy...@amazon.com;
> michael.c...@broadcom.com; Madalin Bucur <madalin.bu...@nxp.com>;
> Ioana Ciornei <ioana.cior...@nxp.com>; jesse.brandeb...@intel.com;
> anthony.l.ngu...@intel.com; sae...@nvidia.com;
> grygorii.stras...@ti.com; ecree.xil...@gmail.com;
> maciej.fijalkow...@intel.com
> Subject: [PATCH v3 bpf-next] bpf: devmap: move drop error path to devmap
> for XDP_REDIRECT
> 
> We want to change the current ndo_xdp_xmit drop semantics because
> it will allow us to implement better queue overflow handling.
> This is working towards the larger goal of a XDP TX queue-hook.
> Move XDP_REDIRECT error path handling from each XDP ethernet driver to
> devmap code. According to the new APIs, the driver running the
> ndo_xdp_xmit pointer, will break tx loop whenever the hw reports a tx
> error and it will just return to devmap caller the number of successfully
> transmitted frames. It will be devmap responsability to free dropped
> frames.
> Move each XDP ndo_xdp_xmit capable driver to the new APIs:
> - veth
> - virtio-net
> - mvneta
> - mvpp2
> - socionext
> - amazon ena
> - bnxt
> - freescale (dpaa2, dpaa)
> - xen-frontend
> - qede
> - ice
> - igb
> - ixgbe
> - i40e
> - mlx5
> - ti (cpsw, cpsw-new)
> - tun
> - sfc
> 
> Acked-by: Edward Cree <ecree.xil...@gmail.com>
> Reviewed-by: Ioana Ciornei <ioana.cior...@nxp.com>
> Reviewed-by: Ilias Apalodimas <ilias.apalodi...@linaro.org>
> Signed-off-by: Lorenzo Bianconi <lore...@kernel.org>

For the dpaa driver:
Reviewed-by: Camelia Groza <camelia.gr...@nxp.com>

Reply via email to