From: Ingo Molnar <mingo@kernel.org>
To: Alexei Starovoitov <ast@plumgrid.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Steven Rostedt <rostedt@goodmis.org>,
Daniel Borkmann <dborkman@redhat.com>,
Chema Gonzalez <chema@google.com>,
Eric Dumazet <edumazet@google.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Jiri Olsa <jolsa@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] split BPF out of core networking
Date: Sun, 1 Jun 2014 10:05:46 +0200 [thread overview]
Message-ID: <20140601080546.GB29062@gmail.com> (raw)
In-Reply-To: <1401586941-4274-1-git-send-email-ast@plumgrid.com>
* Alexei Starovoitov <ast@plumgrid.com> wrote:
> This patch set splits BPF out of core networking into generic component
> net: filter: split filter.c into two files
> net: filter: split BPF out of core networking
>
> arch/Kconfig | 3 +-
> include/linux/filter.h | 2 +
> net/Kconfig | 4 +
> net/Makefile | 1 +
> net/bpf/Makefile | 5 +
> net/bpf/core.c | 1063 ++++++++++++++++++++++++++++++++++++++++++++++++
> net/core/filter.c | 1023 +---------------------------------------------
> 7 files changed, 1079 insertions(+), 1022 deletions(-)
> create mode 100644 net/bpf/Makefile
> create mode 100644 net/bpf/core.c
I like the splitup, but please put it into lib/bpf/ or kernel/bpf/ to
signal its 'generic', 'core' nature, to be used in many subsystems
outside of networking.
Thanks,
Ingo
prev parent reply other threads:[~2014-06-01 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 1:42 [PATCH net-next 0/2] split BPF out of core networking Alexei Starovoitov
2014-06-01 1:42 ` [PATCH net-next 1/2] net: filter: split filter.c into two files Alexei Starovoitov
2014-06-01 1:42 ` [PATCH net-next 2/2] net: filter: split BPF out of core networking Alexei Starovoitov
2014-06-01 8:05 ` Ingo Molnar [this message]
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=20140601080546.GB29062@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=ast@plumgrid.com \
--cc=chema@google.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=edumazet@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.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).