From: Jesper Dangaard Brouer <brouer@redhat.com>
To: netdev@vger.kernel.org
Cc: Daniel Borkmann <borkmann@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Jesper Dangaard Brouer <brouer@redhat.com>
Subject: [bpf-next V2 PATCH 0/3] XDP micro optimizations for redirect
Date: Mon, 03 Sep 2018 09:54:52 +0200 [thread overview]
Message-ID: <153596124879.4754.16274555878412007253.stgit@firesoul> (raw)
This patchset contains XDP micro optimizations for the redirect core.
These are not functional changes. The optimizations revolve around
getting the compiler to layout the code in a way that reflect how XDP
redirect is used.
Today the compiler chooses to inline and uninline (static C functions)
in a suboptimal way, compared to how XDP redirect can be used. Perf
top clearly shows that almost everything gets inlined into the
function call xdp_do_redirect.
The way the compiler chooses to inlines, does not reflect how XDP
redirect is used, as the compile cannot know this.
---
Jesper Dangaard Brouer (3):
xdp: unlikely instrumentation for xdp map redirect
xdp: explicit inline __xdp_map_lookup_elem
xdp: split code for map vs non-map redirect
net/core/filter.c | 64 ++++++++++++++++++++++++++++++-----------------------
1 file changed, 36 insertions(+), 28 deletions(-)
next reply other threads:[~2018-09-03 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 7:54 Jesper Dangaard Brouer [this message]
2018-09-03 7:54 ` [bpf-next V2 PATCH 1/3] xdp: unlikely instrumentation for xdp map redirect Jesper Dangaard Brouer
2018-09-03 7:55 ` [bpf-next V2 PATCH 2/3] xdp: explicit inline __xdp_map_lookup_elem Jesper Dangaard Brouer
2018-09-03 7:55 ` [bpf-next V2 PATCH 3/3] xdp: split code for map vs non-map redirect Jesper Dangaard Brouer
2018-09-06 17:55 ` [bpf-next V2 PATCH 0/3] XDP micro optimizations for redirect Alexei Starovoitov
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=153596124879.4754.16274555878412007253.stgit@firesoul \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=borkmann@iogearbox.net \
--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