From: "Björn Töpel" <bjorn.topel@intel.com>
To: Sridhar Samudrala <sridhar.samudrala@intel.com>,
magnus.karlsson@intel.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
maciej.fijalkowski@intel.com, tom.herbert@intel.com
Subject: Re: [PATCH bpf-next 0/5] Add support for SKIP_BPF flag for AF_XDP sockets
Date: Thu, 15 Aug 2019 14:51:18 +0200 [thread overview]
Message-ID: <bebfb097-5357-91d8-ebc7-2f8ede392ad7@intel.com> (raw)
In-Reply-To: <1565840783-8269-1-git-send-email-sridhar.samudrala@intel.com>
On 2019-08-15 05:46, Sridhar Samudrala wrote:
> This patch series introduces XDP_SKIP_BPF flag that can be specified
> during the bind() call of an AF_XDP socket to skip calling the BPF
> program in the receive path and pass the buffer directly to the socket.
>
> When a single AF_XDP socket is associated with a queue and a HW
> filter is used to redirect the packets and the app is interested in
> receiving all the packets on that queue, we don't need an additional
> BPF program to do further filtering or lookup/redirect to a socket.
>
> Here are some performance numbers collected on
> - 2 socket 28 core Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
> - Intel 40Gb Ethernet NIC (i40e)
>
> All tests use 2 cores and the results are in Mpps.
>
> turbo on (default)
> ---------------------------------------------
> no-skip-bpf skip-bpf
> ---------------------------------------------
> rxdrop zerocopy 21.9 38.5
> l2fwd zerocopy 17.0 20.5
> rxdrop copy 11.1 13.3
> l2fwd copy 1.9 2.0
>
> no turbo : echo 1 > /sys/devices/system/cpu/intel_pstate/no_turbo
> ---------------------------------------------
> no-skip-bpf skip-bpf
> ---------------------------------------------
> rxdrop zerocopy 15.4 29.0
> l2fwd zerocopy 11.8 18.2
> rxdrop copy 8.2 10.5
> l2fwd copy 1.7 1.7
> ---------------------------------------------
>
This work is somewhat similar to the XDP_ATTACH work [1]. Avoiding the
retpoline in the XDP program call is a nice performance boost! I like
the numbers! :-) I also like the idea of adding a flag that just does
what most AF_XDP Rx users want -- just getting all packets of a
certain queue into the XDP sockets.
In addition to Toke's mail, I have some more concerns with the series:
* AFAIU the SKIP_BPF only works for zero-copy enabled sockets. IMO, it
should work for all modes (including XDP_SKB).
* In order to work, a user still needs an XDP program running. That's
clunky. I'd like the behavior that if no XDP program is attached,
and the option is set, the packets for a that queue end up in the
socket. If there's an XDP program attached, the program has
precedence.
* It requires changes in all drivers. Not nice, and scales badly. Try
making it generic (xdp_do_redirect/xdp_flush), so it Just Works for
all XDP capable drivers.
Thanks for working on this!
Björn
[1]
https://lore.kernel.org/netdev/20181207114431.18038-1-bjorn.topel@gmail.com/
> Sridhar Samudrala (5):
> xsk: Convert bool 'zc' field in struct xdp_umem to a u32 bitmap
> xsk: Introduce XDP_SKIP_BPF bind option
> i40e: Enable XDP_SKIP_BPF option for AF_XDP sockets
> ixgbe: Enable XDP_SKIP_BPF option for AF_XDP sockets
> xdpsock_user: Add skip_bpf option
>
> drivers/net/ethernet/intel/i40e/i40e_txrx.c | 22 +++++++++-
> drivers/net/ethernet/intel/i40e/i40e_xsk.c | 6 +++
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 20 ++++++++-
> drivers/net/ethernet/intel/ixgbe/ixgbe_xsk.c | 16 ++++++-
> include/net/xdp_sock.h | 21 ++++++++-
> include/uapi/linux/if_xdp.h | 1 +
> include/uapi/linux/xdp_diag.h | 1 +
> net/xdp/xdp_umem.c | 9 ++--
> net/xdp/xsk.c | 43 ++++++++++++++++---
> net/xdp/xsk_diag.c | 5 ++-
> samples/bpf/xdpsock_user.c | 8 ++++
> 11 files changed, 135 insertions(+), 17 deletions(-)
>
next prev parent reply other threads:[~2019-08-15 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 3:46 [PATCH bpf-next 0/5] Add support for SKIP_BPF flag for AF_XDP sockets Sridhar Samudrala
2019-08-15 3:46 ` [PATCH bpf-next 1/5] xsk: Convert bool 'zc' field in struct xdp_umem to a u32 bitmap Sridhar Samudrala
2019-08-15 3:46 ` [PATCH bpf-next 2/5] xsk: Introduce XDP_SKIP_BPF bind option Sridhar Samudrala
2019-08-15 3:46 ` [PATCH bpf-next 3/5] i40e: Enable XDP_SKIP_BPF option for AF_XDP sockets Sridhar Samudrala
2019-08-16 9:21 ` kbuild test robot
2019-08-15 3:46 ` [PATCH bpf-next 4/5] ixgbe: " Sridhar Samudrala
2019-08-15 3:46 ` [PATCH bpf-next 5/5] xdpsock_user: Add skip_bpf option Sridhar Samudrala
2019-08-15 11:12 ` [PATCH bpf-next 0/5] Add support for SKIP_BPF flag for AF_XDP sockets Toke Høiland-Jørgensen
2019-08-15 16:25 ` Samudrala, Sridhar
2019-08-15 17:11 ` Toke Høiland-Jørgensen
2019-08-16 6:12 ` Samudrala, Sridhar
2019-08-15 12:51 ` Björn Töpel [this message]
2019-08-15 16:46 ` Samudrala, Sridhar
2019-08-16 13:32 ` [Intel-wired-lan] " Björn Töpel
2019-08-16 22:08 ` Jonathan Lemon
2019-08-19 7:39 ` Björn Töpel
2019-08-15 19:28 ` Jakub Kicinski
2019-08-16 6:25 ` Samudrala, Sridhar
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=bebfb097-5357-91d8-ebc7-2f8ede392ad7@intel.com \
--to=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=tom.herbert@intel.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).