From: mgherzan@gmail.com (Mircea Gherzan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7] ARM: net: JIT compiler for packet filters
Date: Mon, 13 Feb 2012 16:36:29 +0100 [thread overview]
Message-ID: <4F392DFD.4070600@gmail.com> (raw)
In-Reply-To: <1325937154-2656-1-git-send-email-mgherzan@gmail.com>
Hi,
Am 07.01.2012 12:52, schrieb Mircea Gherzan:
> Based of Matt Evans's PPC64 implementation.
>
> The compiler generates ARM instructions but interworking is
> supported for Thumb2 kernels.
>
> Supports both little and big endian. Unaligned loads are emitted
> for ARMv6+. Not all the BPF opcodes that deal with ancillary data
> are supported. The scratch memory of the filter lives on the stack.
> Hardware integer division is used if it is available.
>
> Enabled in the same way as for x86-64 and PPC64:
>
> echo 1 > /proc/sys/net/core/bpf_jit_enable
>
> A value greater than 1 enables opcode output.
>
> Signed-off-by: Mircea Gherzan <mgherzan@gmail.com>
> ---
>
> Changes in v7:
> * fix the intruction generation for LDX_MSH, OR_X, LSH_K,
> RSH_K and JMP_JA
> * fix the condition for saving the A register
> * use fls() instead of the compiler builtin
> * punt to the interpreter on absolute loads with K < 0
> * check for invalid data references
> * support the NEG opcode
> * clear X in the prologue based on a context flag
> * simplify the conditional jumps
>
> Changes in v6:
> * fix the code generation for the ANC_CPU opcode
>
> Changes in v5:
> * replace SEEN_LEN with SEEN_SKB
> * set ctx->seen when handling some ancillary data opcodes
>
> Changes in v4:
> * first check if the JIT compiler is enabled
> * fix the code generation for the LDX_MSH opcode
>
> Changes in v3:
> * no longer depend on EABI and !Thumb2
> * add BLX "emulation" for ARMv4 without Thumb
> * use the integer divide instruction on Cortex-A15
> * fix the handling of the DIV_K opcode
> * use a C wrapper for __aeabi_uidiv
> * fix the generation of the epilogue (non-FP case)
>
> Changes in v2:
> * enable the compiler only for ARMv5+ because of the BLX instruction
> * use the same comparison for the ARM version checks
> * use misaligned accesses on ARMv6
> * fix the SEEN_MEM
> * fix the mem_words_used()
>
> arch/arm/Kconfig | 1 +
> arch/arm/Makefile | 1 +
> arch/arm/net/Makefile | 3 +
> arch/arm/net/bpf_jit_32.c | 912 +++++++++++++++++++++++++++++++++++++++++++++
> arch/arm/net/bpf_jit_32.h | 190 ++++++++++
> 5 files changed, 1107 insertions(+), 0 deletions(-)
> create mode 100644 arch/arm/net/Makefile
> create mode 100644 arch/arm/net/bpf_jit_32.c
> create mode 100644 arch/arm/net/bpf_jit_32.h
Gentle ping. This patch has been in the tracking system for over a
month. Is there any reason not to apply it in arm/for-next?
Thanks,
Mircea
next prev parent reply other threads:[~2012-02-13 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 11:52 [PATCH v7] ARM: net: JIT compiler for packet filters Mircea Gherzan
2012-01-09 7:14 ` Eric Dumazet
2012-01-09 8:58 ` Mircea Gherzan
2012-02-13 15:36 ` Mircea Gherzan [this message]
2012-02-13 16:02 ` Russell King - ARM Linux
2012-03-15 7:23 ` Mircea Gherzan
2012-03-15 11:41 ` Russell King - ARM Linux
2012-03-16 7:53 ` Mircea Gherzan
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=4F392DFD.4070600@gmail.com \
--to=mgherzan@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).