From: Alexei Starovoitov <ast@plumgrid.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] net: filter: split eBPF interpreter out of core networking
Date: Tue, 22 Jul 2014 23:01:57 -0700 [thread overview]
Message-ID: <1406095319-3627-1-git-send-email-ast@plumgrid.com> (raw)
Hi David,
I believe my recent set of RFC/patches [1] provided good visibility on where
I would like to take eBPF subsystem. These two trivial patches is a first step
in that direction:
patch 1 - mechanical split of eBPF interpreter out of filter.c
patch 2 - nominate myself as a maintainer for eBPF core pieces
In the foreseeable future eBPF patches will be going through net-next,
so put netdev as a primary mailing list
[1] git://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf master
Alexei Starovoitov (2):
net: filter: split filter.c into two files
bpf: update MAINTAINERS entry
MAINTAINERS | 7 +
kernel/Makefile | 1 +
kernel/bpf/Makefile | 1 +
kernel/bpf/core.c | 536 +++++++++++++++++++++++++++++++++++++++++++++++++++
net/core/filter.c | 511 ------------------------------------------------
5 files changed, 545 insertions(+), 511 deletions(-)
create mode 100644 kernel/bpf/Makefile
create mode 100644 kernel/bpf/core.c
--
1.7.9.5
next reply other threads:[~2014-07-23 6:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 6:01 Alexei Starovoitov [this message]
2014-07-23 6:01 ` [PATCH net-next 1/2] net: filter: split filter.c into two files Alexei Starovoitov
2014-07-23 6:11 ` Varka Bhadram
2014-07-23 8:26 ` David Laight
2014-07-23 8:54 ` Daniel Borkmann
2014-07-23 16:49 ` Alexei Starovoitov
2014-07-24 23:45 ` Valdis.Kletnieks
2014-07-24 23:58 ` Alexei Starovoitov
2014-07-25 0:48 ` Valdis.Kletnieks
2014-07-23 6:01 ` [PATCH net-next 2/2] bpf: update MAINTAINERS entry Alexei Starovoitov
2014-07-24 4:08 ` [PATCH net-next 0/2] net: filter: split eBPF interpreter out of core networking David Miller
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=1406095319-3627-1-git-send-email-ast@plumgrid.com \
--to=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).