From: "Björn Töpel" <bjorn.topel@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org
Cc: "Björn Töpel" <bjorn.topel@gmail.com>,
bjorn.topel@intel.com, maciej.fijalkowski@intel.com,
hawk@kernel.org, toke@redhat.com, magnus.karlsson@intel.com,
john.fastabend@gmail.com, kuba@kernel.org, davem@davemloft.net
Subject: [PATCH bpf-next v5 0/2] Optimize bpf_redirect_map()/xdp_do_redirect()
Date: Sat, 27 Feb 2021 13:21:37 +0100 [thread overview]
Message-ID: <20210227122139.183284-1-bjorn.topel@gmail.com> (raw)
Hi XDP-folks,
This two patch series contain two optimizations for the
bpf_redirect_map() helper and the xdp_do_redirect() function.
The bpf_redirect_map() optimization is about avoiding the map lookup
dispatching. Instead of having a switch-statement and selecting the
correct lookup function, we let bpf_redirect_map() be a map operation,
where each map has its own bpf_redirect_map() implementation. This way
the run-time lookup is avoided.
The xdp_do_redirect() patch restructures the code, so that the map
pointer indirection can be avoided.
Performance-wise I got 4% improvement for XSKMAP
(sample:xdpsock/rx-drop), and 8% (sample:xdp_redirect_map) on my
machine.
More details in each commit.
Changelog:
v4->v5: Renamed map operation to map_redirect. (Daniel)
v3->v4: Made bpf_redirect_map() a map operation. (Daniel)
v2->v3: Fix build when CONFIG_NET is not set. (lkp)
v1->v2: Removed warning when CONFIG_BPF_SYSCALL was not set. (lkp)
Cleaned up case-clause in xdp_do_generic_redirect_map(). (Toke)
Re-added comment. (Toke)
rfc->v1: Use map_id, and remove bpf_clear_redirect_map(). (Toke)
Get rid of the macro and use __always_inline. (Jesper)
rfc: https://lore.kernel.org/bpf/87im7fy9nc.fsf@toke.dk/ (Cover not on lore!)
v1: https://lore.kernel.org/bpf/20210219145922.63655-1-bjorn.topel@gmail.com/
v2: https://lore.kernel.org/bpf/20210220153056.111968-1-bjorn.topel@gmail.com/
v3: https://lore.kernel.org/bpf/20210221200954.164125-3-bjorn.topel@gmail.com/
v4: https://lore.kernel.org/bpf/20210226112322.144927-1-bjorn.topel@gmail.com/
Cheers,
Björn
Björn Töpel (2):
bpf, xdp: make bpf_redirect_map() a map operation
bpf, xdp: restructure redirect actions
include/linux/bpf.h | 26 ++----
include/linux/filter.h | 39 +++++++-
include/net/xdp_sock.h | 19 ----
include/trace/events/xdp.h | 66 ++++++++-----
kernel/bpf/cpumap.c | 10 +-
kernel/bpf/devmap.c | 19 +++-
kernel/bpf/verifier.c | 11 ++-
net/core/filter.c | 183 ++++++++++++-------------------------
net/xdp/xskmap.c | 20 +++-
9 files changed, 195 insertions(+), 198 deletions(-)
base-commit: 85e142cb42a1e7b33971bf035dae432d8670c46b
--
2.27.0
next reply other threads:[~2021-02-27 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 12:21 Björn Töpel [this message]
2021-02-27 12:21 ` [PATCH bpf-next v5 1/2] bpf, xdp: make bpf_redirect_map() a map operation Björn Töpel
2021-03-05 15:55 ` Daniel Borkmann
2021-03-05 17:11 ` Björn Töpel
2021-02-27 12:21 ` [PATCH bpf-next v5 2/2] bpf, xdp: restructure redirect actions Björn Töpel
2021-03-05 15:44 ` Daniel Borkmann
2021-03-05 17:11 ` Björn Töpel
2021-03-05 22:56 ` Daniel Borkmann
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=20210227122139.183284-1-bjorn.topel@gmail.com \
--to=bjorn.topel@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.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).