From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Alexei Starovoitov <ast@plumgrid.com>,
"David S. Miller" <davem@davemloft.net>,
Ingo Molnar <mingo@kernel.org>,
Daniel Borkmann <dborkman@redhat.com>,
Chema Gonzalez <chema@google.com>,
Eric Dumazet <edumazet@google.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] split BPF out of core networking
Date: Mon, 2 Jun 2014 11:16:06 -0300 [thread overview]
Message-ID: <20140602141606.GC2544@kernel.org> (raw)
In-Reply-To: <20140602092456.2114440a@gandalf.local.home>
Em Mon, Jun 02, 2014 at 09:24:56AM -0400, Steven Rostedt escreveu:
> On Mon, 2 Jun 2014 08:15:45 -0500
> Jonathan Corbet <corbet@lwn.net> wrote:
> > On Mon, 2 Jun 2014 00:01:44 -0700
> > Alexei Starovoitov <ast@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.
- Arnaldo
next prev parent reply other threads:[~2014-06-02 14:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 7:01 [PATCH v2 net-next 0/2] split BPF out of core networking Alexei Starovoitov
2014-06-02 7:01 ` [PATCH v2 net-next 1/2] net: filter: split filter.c into two files Alexei Starovoitov
2014-06-02 7:01 ` [PATCH v2 net-next 2/2] net: filter: split BPF out of core networking Alexei Starovoitov
2014-06-02 8:57 ` [PATCH v2 net-next 0/2] " Daniel Borkmann
2014-06-02 15:41 ` Alexei Starovoitov
2014-06-02 17:04 ` Daniel Borkmann
2014-06-02 19:02 ` Alexei Starovoitov
2014-06-03 8:56 ` Daniel Borkmann
2014-06-03 15:44 ` Alexei Starovoitov
2014-06-03 20:35 ` Daniel Borkmann
2014-06-03 20:58 ` Alexei Starovoitov
2014-06-03 21:40 ` Chema Gonzalez
2014-06-04 0:38 ` Alexei Starovoitov
2014-06-20 16:44 ` Chema Gonzalez
2014-06-23 9:18 ` David Laight
2014-06-23 21:57 ` Alexei Starovoitov
2014-06-24 8:33 ` Daniel Borkmann
2014-06-02 13:15 ` Jonathan Corbet
2014-06-02 13:24 ` Steven Rostedt
2014-06-02 14:16 ` Arnaldo Carvalho de Melo [this message]
2014-06-02 14:57 ` Alexei Starovoitov
2014-06-03 18:16 ` Ingo Molnar
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=20140602141606.GC2544@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=ast@plumgrid.com \
--cc=chema@google.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=edumazet@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).