LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Matt Evans <matt@ozlabs.org>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3] net: filter: BPF 'JIT' compiler for PPC64
Date: Thu, 21 Jul 2011 07:00:19 +0200	[thread overview]
Message-ID: <1311224419.2570.6.camel@edumazet-laptop> (raw)
In-Reply-To: <4E278604.5080605@ozlabs.org>

Le jeudi 21 juillet 2011 à 11:51 +1000, Matt Evans a écrit :
> An implementation of a code generator for BPF programs to speed up packet
> filtering on PPC64, inspired by Eric Dumazet's x86-64 version.
> 
> Filter code is generated as an ABI-compliant function in module_alloc()'d mem
> with stackframe & prologue/epilogue generated if required (simple filters don't
> need anything more than an li/blr).  The filter's local variables, M[], live in
> registers.  Supports all BPF opcodes, although "complicated" loads from negative
> packet offsets (e.g. SKF_LL_OFF) are not yet supported.
> 
> There are a couple of further optimisations left for future work; many-pass
> assembly with branch-reach reduction and a register allocator to push M[]
> variables into volatile registers would improve the code quality further.
> 
> This currently supports big-endian 64-bit PowerPC only (but is fairly simple
> to port to PPC32 or LE!).
> 
> Enabled in the same way as x86-64:
> 
> 	echo 1 > /proc/sys/net/core/bpf_jit_enable
> 
> Or, enabled with extra debug output:
> 
> 	echo 2 > /proc/sys/net/core/bpf_jit_enable
> 
> Signed-off-by: Matt Evans <matt@ozlabs.org>
> ---
> 
> V3: Added BUILD_BUG_ON to assert PACA CPU ID is 16bits, made a comment (in
>     LD_MSH) a bit clearer, ratelimited "Unknown opcode" error and moved
>     bpf_jit.S to bpf_jit_64.S (it doesn't make sense to rename bpf_jit_comp.c as
>     small portions will eventually get split out into _32/_64.c files when we do
>     32bit support).
> 
>  arch/powerpc/Kconfig                  |    1 +
>  arch/powerpc/Makefile                 |    3 +-
>  arch/powerpc/include/asm/ppc-opcode.h |   40 ++
>  arch/powerpc/net/Makefile             |    4 +
>  arch/powerpc/net/bpf_jit.h            |  227 +++++++++++
>  arch/powerpc/net/bpf_jit_64.S         |  138 +++++++
>  arch/powerpc/net/bpf_jit_comp.c       |  694 +++++++++++++++++++++++++++++++++
>  7 files changed, 1106 insertions(+), 1 deletions(-)

Nice work Matt ;)

Acked-by: Eric Dumazet <eric.dumazet@gmail.com>

Thanks

  reply	other threads:[~2011-07-21  5:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18  7:50 [PATCH] net: filter: BPF 'JIT' compiler for PPC64 Matt Evans
2011-07-18  8:39 ` Eric Dumazet
2011-07-18 19:42   ` David Miller
2011-07-18 20:05     ` Eric Dumazet
2011-07-19  1:21     ` Matt Evans
2011-07-19  2:13 ` [PATCH v2] " Matt Evans
2011-07-19  6:51   ` Eric Dumazet
2011-07-19  7:55     ` Benjamin Herrenschmidt
2011-07-19  9:06       ` Eric Dumazet
2011-07-19  9:22         ` Benjamin Herrenschmidt
2011-07-19  6:59   ` Kumar Gala
2011-07-19  7:06     ` Matt Evans
2011-07-19  7:17       ` Kumar Gala
2011-07-19  7:23         ` Matt Evans
2011-07-21  1:51   ` [PATCH v3] " Matt Evans
2011-07-21  5:00     ` Eric Dumazet [this message]
2011-07-21 19:47     ` David Miller

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=1311224419.2570.6.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=matt@ozlabs.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