From: David Miller <davem@davemloft.net>
To: ast@plumgrid.com
Cc: geert@linux-m68k.org, josh@joshtriplett.org, mingo@kernel.org,
rostedt@goodmis.org, hannes@stressinduktion.org,
edumazet@google.com, dborkman@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] bpf: split eBPF out of NET
Date: Mon, 27 Oct 2014 19:10:43 -0400 (EDT) [thread overview]
Message-ID: <20141027.191043.246099210901442100.davem@davemloft.net> (raw)
In-Reply-To: <1414114868-28228-1-git-send-email-ast@plumgrid.com>
From: Alexei Starovoitov <ast@plumgrid.com>
Date: Thu, 23 Oct 2014 18:41:08 -0700
> introduce two configs:
> - hidden CONFIG_BPF to select eBPF interpreter that classic socket filters
> depend on
> - visible CONFIG_BPF_SYSCALL (default off) that tracing and sockets can use
>
> that solves several problems:
> - tracing and others that wish to use eBPF don't need to depend on NET.
> They can use BPF_SYSCALL to allow loading from userspace or select BPF
> to use it directly from kernel in NET-less configs.
> - in 3.18 programs cannot be attached to events yet, so don't force it on
> - when the rest of eBPF infra is there in 3.19+, it's still useful to
> switch it off to minimize kernel size
>
> Signed-off-by: Alexei Starovoitov <ast@plumgrid.com>
> ---
>
> bloat-o-meter on x64 shows:
> add/remove: 0/60 grow/shrink: 0/2 up/down: 0/-15601 (-15601)
>
> tested with many different config combinations. Hopefully didn't miss anything.
Applied with two changes:
1) boolean --> bool
2) Moved bloat-o-meter and testing information into commit message.
Thanks.
next prev parent reply other threads:[~2014-10-27 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 1:41 [PATCH net] bpf: split eBPF out of NET Alexei Starovoitov
2014-10-24 3:23 ` Josh Triplett
2014-10-24 5:32 ` Alexei Starovoitov
2014-10-24 8:11 ` Josh Triplett
2014-10-24 8:19 ` Geert Uytterhoeven
2014-10-24 8:37 ` Daniel Borkmann
2014-10-27 23:10 ` David Miller [this message]
2014-10-28 0:18 ` 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=20141027.191043.246099210901442100.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@plumgrid.com \
--cc=dborkman@redhat.com \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=hannes@stressinduktion.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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).