On Mon, Jun 2, 2014 at 7:16 AM, Arnaldo Carvalho de Melo <a...@kernel.org> wrote: > Em Mon, Jun 02, 2014 at 09:24:56AM -0400, Steven Rostedt escreveu: >> On Mon, 2 Jun 2014 08:15:45 -0500 >> Jonathan Corbet <cor...@lwn.net> wrote: > >> > On Mon, 2 Jun 2014 00:01:44 -0700 >> > Alexei Starovoitov <a...@plumgrid.com> wrote: > >> > > This patch set splits BPF out of core networking into generic component > >> > Quick, probably dumb question: if you're going to split it out, why not >> > split it out entirely, into kernel/ or (perhaps better) lib/? The >> > whole point seems to be that BPF is outgrowing its networking home, so >> > it seems like it might be better to make it truly generic. > >> I believe this is what Ingo suggested as well. If it is become generic, >> it belongs in lib/ > > Yes, that was his suggestion, which I agree with, FWIW.
I guess I posted v2 too quickly :) v2 splits filter.c into kernel/bpf/. I think it's a better location than lib/bpf, since lib feels too constrained by definition of 'library'. bpf is more than a set of library calls. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
