|author||Alexei Starovoitov <email@example.com>||2014-10-23 18:41:08 -0700|
|committer||David S. Miller <firstname.lastname@example.org>||2014-10-27 19:09:59 -0400|
bpf: split eBPF out of NET
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 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. Signed-off-by: Alexei Starovoitov <email@example.com> Acked-by: Daniel Borkmann <firstname.lastname@example.org> Signed-off-by: David S. Miller <email@example.com>
Diffstat (limited to 'net')
1 files changed, 1 insertions, 1 deletions
diff --git a/net/Kconfig b/net/Kconfig
index 6272420a721b..99815b5454bf 100644
@@ -6,7 +6,7 @@ menuconfig NET
bool "Networking support"
- select ANON_INODES
+ select BPF
Unless you really know what you are doing, you should say Y here.
The reason is that some programs need kernel networking support even