[PATCH] [RFC PATCH] BPF backend
Joerg Sonnenberger
joerg at britannica.bec.de
Thu Dec 4 03:56:19 PST 2014
On Wed, Dec 03, 2014 at 03:07:41PM -0800, Alexei Starovoitov wrote:
> On Wed, Dec 3, 2014 at 2:44 PM, Joerg Sonnenberger
> <joerg at britannica.bec.de> wrote:
> > On Wed, Dec 03, 2014 at 03:08:17AM +0000, Alexei Starovoitov wrote:
> >> recently linux gained "universal in-kernel virtual machine" which is called
> >> eBPF or extended BPF. The name comes from "Berkeley Packet Filter", since
> >> new instruction set is based on it.
> >
> > I'd prefer if the backend name matches that, e.g. eBPF and not BPF.
>
> What had similar discussion in kernel and common agreement was to use
> just BPF everywhere. In all macros, filenames, system call, etc.
> It will be extremely confusing to users when they can do 'man bpf'
> and #include <bpf.h>, but to select correct llvm backend they
> would have to specify -march=ebpf...
It will be just as confusion for users on any non-Linux system to
discover that the created BPF is not really BPF. I blame the Linux folks
for overloading the name.
Joerg
More information about the llvm-commits
mailing list