From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, davem@davemloft.net,
kuba@kernel.org, ast@kernel.org, lorenzo.bianconi@redhat.com,
brouer@redhat.com, toke@redhat.com, freysteinn.alfredsson@kau.se
Subject: Re: [PATCH bpf-next] bpf: devmap: move drop error path to devmap for XDP_REDIRECT
Date: Sat, 27 Feb 2021 11:16:33 +0100 [thread overview]
Message-ID: <YDocAXK6K4bg/olY@lore-desk> (raw)
In-Reply-To: <c3b56d02-e415-b6e9-2c22-9c3d341e07e9@iogearbox.net>
[-- Attachment #1: Type: text/plain, Size: 1977 bytes --]
> On 2/17/21 2:56 PM, Lorenzo Bianconi wrote:
> > 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
>
> I presume for a number of these drivers the refactoring changes were just compile-
> tested due to lack of HW, right? If so, please also Cc related driver maintainers
> aside from the few of us, so they have a chance to review & ACK the patch if it looks
> good to them. I presume Ed saw it by accident, but for others it might easily get
> lost in the daily mail flood.
Hi Daniel,
ack, I will do in v2.
>
> > More details about the new ndo_xdp_xmit design can be found here [0].
> >
> > [0] https://github.com/xdp-project/xdp-project/blob/master/areas/core/redesign01_ndo_xdp_xmit.org
>
> I'd probably move this below the "---" if it's not essential to the commit itself or
> rather take relevant parts out and move it into the commit desc so it doesn't get
> lost for future ref given things could likely reschuffle inside the repo in the future,
> just a nit.
ack, I will do in v2.
Regards,
Lorenzo
>
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2021-02-27 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 13:56 [PATCH bpf-next] bpf: devmap: move drop error path to devmap for XDP_REDIRECT Lorenzo Bianconi
2021-02-17 20:15 ` Edward Cree
2021-02-27 0:09 ` Daniel Borkmann
2021-02-27 10:16 ` Lorenzo Bianconi [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=YDocAXK6K4bg/olY@lore-desk \
--to=lorenzo@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=freysteinn.alfredsson@kau.se \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.com \
/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).