linux-kernel - Re: v3.18-rc1 bloat-o-meter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAADnVQJsbNHs-S9gMF7P6FwHvHTfFSTPGNTLXAo5tJ8mpB5t6Q@mail.gmail.com>
Date:	Mon, 20 Oct 2014 17:57:30 +0200
From:	Alexei Starovoitov <alexei.starovoitov@...il.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	linux-embedded@...r.kernel.org,
	Josh Triplett <josh@...htriplett.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: v3.18-rc1 bloat-o-meter

On Mon, Oct 20, 2014 at 10:37 AM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
>         Hi all,
>
> Below is the bloat-o-meter output when comparing an m68k/atari_defconfig
> kernel for v3.17 and v3.18-rc1.
>
> Major culprit seems to be bpf. Can this become modular or optional?
> Currently it's always included if CONFIG_NET=y.

yes, the plan is to get it its own CONFIG_BPF so that tracing wouldn't
need to depend on whole NET and so it can be stubbed out.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/