From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Camelia Groza <camelia.groza@nxp.com>
Cc: kuba@kernel.org, davem@davemloft.net, madalin.bucur@oss.nxp.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net 1/3] dpaa_eth: reserve space for the xdp_frame under the A050385 erratum
Date: Thu, 4 Feb 2021 09:51:58 +0100 [thread overview]
Message-ID: <20210204085158.GA2580@ranger.igk.intel.com> (raw)
In-Reply-To: <b2e61a1ac55004ecbbe326cd878cd779df22aae8.1612275417.git.camelia.groza@nxp.com>
On Tue, Feb 02, 2021 at 07:34:42PM +0200, Camelia Groza wrote:
> When the erratum workaround is triggered, the newly created xdp_frame
> structure is stored at the start of the newly allocated buffer. Avoid
> the structure from being overwritten by explicitly reserving enough
> space in the buffer for storing it.
>
> Account for the fact that the structure's size might increase in time by
> aligning the headroom to DPAA_FD_DATA_ALIGNMENT bytes, thus guaranteeing
> the data's alignment.
>
> Fixes: ae680bcbd06a ("dpaa_eth: implement the A050385 erratum workaround for XDP")
> Signed-off-by: Camelia Groza <camelia.groza@nxp.com>
> ---
> drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c b/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
> index 4360ce4d3fb6..e1d041c35ad9 100644
> --- a/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
> +++ b/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
> @@ -2182,6 +2182,7 @@ static int dpaa_a050385_wa_xdpf(struct dpaa_priv *priv,
> struct xdp_frame *new_xdpf, *xdpf = *init_xdpf;
> void *new_buff;
> struct page *p;
> + int headroom;
>
> /* Check the data alignment and make sure the headroom is large
> * enough to store the xdpf backpointer. Use an aligned headroom
> @@ -2197,19 +2198,31 @@ static int dpaa_a050385_wa_xdpf(struct dpaa_priv *priv,
> return 0;
> }
>
> + /* The new xdp_frame is stored in the new buffer. Reserve enough space
> + * in the headroom for storing it along with the driver's private
> + * info. The headroom needs to be aligned to DPAA_FD_DATA_ALIGNMENT to
> + * guarantee the data's alignment in the buffer.
> + */
> + headroom = ALIGN(sizeof(*new_xdpf) + priv->tx_headroom,
> + DPAA_FD_DATA_ALIGNMENT);
> +
> + /* Assure the extended headroom and data fit in a one-paged buffer */
> + if (headroom + xdpf->len > DPAA_BP_RAW_SIZE)
This check might make more sense if you would be accounting for
skb_shared_info as well I suppose, so that you know you'll still provide
enough tailroom for future xdp multibuf support. Didn't all the previous
code path make sure that there's a room for that?
> + return -ENOMEM;
> +
> p = dev_alloc_pages(0);
> if (unlikely(!p))
> return -ENOMEM;
>
> /* Copy the data to the new buffer at a properly aligned offset */
> new_buff = page_address(p);
> - memcpy(new_buff + priv->tx_headroom, xdpf->data, xdpf->len);
> + memcpy(new_buff + headroom, xdpf->data, xdpf->len);
>
> /* Create an XDP frame around the new buffer in a similar fashion
> * to xdp_convert_buff_to_frame.
> */
> new_xdpf = new_buff;
> - new_xdpf->data = new_buff + priv->tx_headroom;
> + new_xdpf->data = new_buff + headroom;
> new_xdpf->len = xdpf->len;
> new_xdpf->headroom = priv->tx_headroom;
> new_xdpf->frame_sz = DPAA_BP_RAW_SIZE;
> --
> 2.17.1
>
next prev parent reply other threads:[~2021-02-04 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 17:34 [PATCH net 0/3] dpaa_eth: A050385 erratum workaround fixes under XDP Camelia Groza
2021-02-02 17:34 ` [PATCH net 1/3] dpaa_eth: reserve space for the xdp_frame under the A050385 erratum Camelia Groza
2021-02-04 8:51 ` Maciej Fijalkowski [this message]
2021-02-04 11:55 ` Camelia Alexandra Groza
2021-02-02 17:34 ` [PATCH net 2/3] dpaa_eth: reduce data alignment requirements for " Camelia Groza
2021-02-04 15:58 ` Maciej Fijalkowski
2021-02-02 17:34 ` [PATCH net 3/3] dpaa_eth: try to move the data in place " Camelia Groza
2021-02-04 15:56 ` Maciej Fijalkowski
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=20210204085158.GA2580@ranger.igk.intel.com \
--to=maciej.fijalkowski@intel.com \
--cc=camelia.groza@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=madalin.bucur@oss.nxp.com \
--cc=netdev@vger.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).