From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Camelia Groza <camelia.groza@nxp.com>
Cc: kuba@kernel.org, brouer@redhat.com, saeed@kernel.org,
davem@davemloft.net, madalin.bucur@oss.nxp.com,
ioana.ciornei@nxp.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/7] dpaa_eth: add XDP support
Date: Sat, 28 Nov 2020 23:59:57 +0100 [thread overview]
Message-ID: <20201128225957.GA45349@ranger.igk.intel.com> (raw)
In-Reply-To: <cover.1606322126.git.camelia.groza@nxp.com>
On Wed, Nov 25, 2020 at 06:53:29PM +0200, Camelia Groza wrote:
> Enable XDP support for the QorIQ DPAA1 platforms.
>
> Implement all the current actions (DROP, ABORTED, PASS, TX, REDIRECT). No
> Tx batching is added at this time.
>
> Additional XDP_PACKET_HEADROOM bytes are reserved in each frame's headroom.
>
> After transmit, a reference to the xdp_frame is saved in the buffer for
> clean-up on confirmation in a newly created structure for software
> annotations. DPAA_TX_PRIV_DATA_SIZE bytes are reserved in the buffer for
> storing this structure and the XDP program is restricted from accessing
> them.
>
> The driver shares the egress frame queues used for XDP with the network
> stack. The DPAA driver is a LLTX driver so no explicit locking is required
> on transmission.
>
> Changes in v2:
> - warn only once if extracting the timestamp from a received frame fails
> in 2/7
>
> Changes in v3:
> - drop received S/G frames when XDP is enabled in 2/7
>
> Changes in v4:
> - report a warning if the MTU is too hight for running XDP in 2/7
> - report an error if opening the device fails in the XDP setup in 2/7
> - call xdp_rxq_info_is_reg() before unregistering in 4/7
> - minor cleanups (remove unneeded variable, print error code) in 4/7
> - add more details in the commit message in 4/7
> - did not call qman_destroy_fq() in case of xdp_rxq_info_reg() failure
> since it would lead to a double free of the fq resources in 4/7
>
> Changes in v5:
> - report errors on XDP setup with extack in 2/7
> - checkpath fix in 4/7
> - add more details in the commit message in 4/7
> - reduce the impact of the A050385 erratum workaround code on non-erratum
> platforms in 7/7
For the series:
Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
>
> Camelia Groza (7):
> dpaa_eth: add struct for software backpointers
> dpaa_eth: add basic XDP support
> dpaa_eth: limit the possible MTU range when XDP is enabled
> dpaa_eth: add XDP_TX support
> dpaa_eth: add XDP_REDIRECT support
> dpaa_eth: rename current skb A050385 erratum workaround
> dpaa_eth: implement the A050385 erratum workaround for XDP
>
> drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 465 +++++++++++++++++++++++--
> drivers/net/ethernet/freescale/dpaa/dpaa_eth.h | 13 +
> 2 files changed, 448 insertions(+), 30 deletions(-)
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2020-11-28 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 16:53 [PATCH net-next v5 0/7] dpaa_eth: add XDP support Camelia Groza
2020-11-25 16:53 ` [PATCH net-next v5 1/7] dpaa_eth: add struct for software backpointers Camelia Groza
2020-11-25 16:53 ` [PATCH net-next v5 2/7] dpaa_eth: add basic XDP support Camelia Groza
2020-11-25 16:53 ` [PATCH net-next v5 3/7] dpaa_eth: limit the possible MTU range when XDP is enabled Camelia Groza
2020-11-25 16:53 ` [PATCH net-next v5 4/7] dpaa_eth: add XDP_TX support Camelia Groza
2020-11-25 16:53 ` [PATCH net-next v5 5/7] dpaa_eth: add XDP_REDIRECT support Camelia Groza
2020-11-25 16:53 ` [PATCH net-next v5 6/7] dpaa_eth: rename current skb A050385 erratum workaround Camelia Groza
2020-11-25 16:53 ` [PATCH net-next v5 7/7] dpaa_eth: implement the A050385 erratum workaround for XDP Camelia Groza
2020-11-28 22:59 ` Maciej Fijalkowski [this message]
2020-12-01 1:34 ` [PATCH net-next v5 0/7] dpaa_eth: add XDP support Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201128225957.GA45349@ranger.igk.intel.com \
--to=maciej.fijalkowski@intel.com \
--cc=brouer@redhat.com \
--cc=camelia.groza@nxp.com \
--cc=davem@davemloft.net \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=madalin.bucur@oss.nxp.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).