From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, jaswinder.singh@linaro.org,
davem@davemloft.net, brouer@redhat.com, lorenzo@kernel.org
Subject: Re: [PATCH] net: netsec: Correct dma sync for XDP_TX frames
Date: Thu, 17 Oct 2019 09:49:31 +0300 [thread overview]
Message-ID: <20191017064931.GA12128@apalos.home> (raw)
In-Reply-To: <20191016171401.16cb1bd5@cakuba.netronome.com>
Hi Jakub,
On Wed, Oct 16, 2019 at 05:14:01PM -0700, Jakub Kicinski wrote:
> On Wed, 16 Oct 2019 14:40:32 +0300, Ilias Apalodimas wrote:
> > bpf_xdp_adjust_head() can change the frame boundaries. Account for the
> > potential shift properly by calculating the new offset before
> > syncing the buffer to the device for XDP_TX
> >
> > Fixes: ba2b232108d3 ("net: netsec: add XDP support")
> > Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
>
> Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com>
>
> You should target this to the bpf or net tree (appropriate [PATCH xyz]
> marking). Although I must admit it's unclear to me as well whether the
> driver changes should be picked up by bpf maintainers or Dave :S
My bad i forgot to add the net-next tag. I'd prefer Dave picking that up, since
he picked all the XDP-related patches for this driver before.
Dave shall i re-send with the proper tag?
>
> > diff --git a/drivers/net/ethernet/socionext/netsec.c b/drivers/net/ethernet/socionext/netsec.c
> > index f9e6744d8fd6..41ddd8fff2a7 100644
> > --- a/drivers/net/ethernet/socionext/netsec.c
> > +++ b/drivers/net/ethernet/socionext/netsec.c
> > @@ -847,8 +847,8 @@ static u32 netsec_xdp_queue_one(struct netsec_priv *priv,
> > enum dma_data_direction dma_dir =
> > page_pool_get_dma_dir(rx_ring->page_pool);
> >
> > - dma_handle = page_pool_get_dma_addr(page) +
> > - NETSEC_RXBUF_HEADROOM;
> > + dma_handle = page_pool_get_dma_addr(page) + xdpf->headroom +
> > + sizeof(*xdpf);
>
> very nitpick: I'd personally write addr + sizeof(*xdpf) + xdpf->headroom
> since that's the order in which they appear in memory
>
> But likely not worth reposting for just that :)
Isn't sizeof static anyway? If Dave needs a v2 with the proper tag i'll change
this as well
>
> > dma_sync_single_for_device(priv->dev, dma_handle, xdpf->len,
> > dma_dir);
> > tx_desc.buf_type = TYPE_NETSEC_XDP_TX;
>
Thanks
/Ilias
prev parent reply other threads:[~2019-10-17 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 11:40 [PATCH] net: netsec: Correct dma sync for XDP_TX frames Ilias Apalodimas
2019-10-17 0:14 ` Jakub Kicinski
2019-10-17 6:49 ` Ilias Apalodimas [this message]
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=20191017064931.GA12128@apalos.home \
--to=ilias.apalodimas@linaro.org \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jaswinder.singh@linaro.org \
--cc=lorenzo@kernel.org \
--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).