Subject: Re: [PATCH v4 net-next 1/3] Extended BPF interpreter and converter

From: Hagen Paul Pfeifer <[email-masked]>
Date: Tue, 4 Mar 2014 14:28:24 +0000

If all issues raised by Daniel are addresed:

Acked-by: Hagen Paul Pfeifer <[email-masked]>

But ...

>Future work:
>
>0. seccomp
>
>1. add extended BPF JIT for x86_64
>
>2. add inband old/new demux and extended BPF verifier, so that new programs
>   can be loaded through old sk_attach_filter() and sk_unattached_filter_create()
>   interfaces
>
>3. tracing filters systemtap-like with extended BPF
>
>4. OVS with extended BPF
>
>5. nftables with extended BPF

... this is shit (not your fault). (Jitted) BPF envolved into a direction
which is just not the right way to do it. You try to fix things, bypass
architectural shortcomings of BPF, perf issues because and so on.

The right direction is to write a new general purpose in-kernel interpreter
from scratch. Capability layers should provide an compatible API for BPF and
seccomp. You have the knowledge to do exactly this, you nearly already did
this - you should start this undertake!

-- 
Hagen Paul Pfeifer