From: Daniel Borkmann <daniel@iogearbox.net>
To: ast@kernel.org
Cc: netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf-next 0/6] Few x64 jit improvements to shrink image size
Date: Sat, 24 Feb 2018 01:07:57 +0100 [thread overview]
Message-ID: <cover.1519430515.git.daniel@iogearbox.net> (raw)
Couple of minor improvements to the x64 JIT I had still around from
pre merge window in order to shrink the image size further. Added
test cases for kselftests too as well as running Cilium workloads on
them w/o issues.
Thanks!
Daniel Borkmann (6):
bpf, x64: save one byte per shl/shr/sar when imm is 1
bpf, x64: save several bytes by using mov over movabsq when possible
bpf, x64: save several bytes when mul dest is r0/r3 anyway
bpf, x64: save few bytes when mul is in alu32
bpf, x64: save 5 bytes in prologue when ebpf insns came from cbpf
bpf: add various jit test cases
arch/x86/net/bpf_jit_comp.c | 219 +++++++++++++++++-----------
tools/testing/selftests/bpf/test_verifier.c | 89 +++++++++++
2 files changed, 221 insertions(+), 87 deletions(-)
--
2.9.5
next reply other threads:[~2018-02-24 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 0:07 Daniel Borkmann [this message]
2018-02-24 0:07 ` [PATCH bpf-next 1/6] bpf, x64: save one byte per shl/shr/sar when imm is 1 Daniel Borkmann
2018-02-24 0:07 ` [PATCH bpf-next 2/6] bpf, x64: save several bytes by using mov over movabsq when possible Daniel Borkmann
2018-02-24 0:08 ` [PATCH bpf-next 3/6] bpf, x64: save several bytes when mul dest is r0/r3 anyway Daniel Borkmann
2018-02-24 0:08 ` [PATCH bpf-next 4/6] bpf, x64: save few bytes when mul is in alu32 Daniel Borkmann
2018-02-24 0:08 ` [PATCH bpf-next 5/6] bpf, x64: save 5 bytes in prologue when ebpf insns came from cbpf Daniel Borkmann
2018-02-24 0:08 ` [PATCH bpf-next 6/6] bpf: add various jit test cases Daniel Borkmann
2018-02-24 7:01 ` [PATCH bpf-next 0/6] Few x64 jit improvements to shrink image size 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=cover.1519430515.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@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).