From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@plumgrid.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/8] eBPF support for cls_bpf
Date: Sun, 01 Mar 2015 14:05:45 -0500 (EST) [thread overview]
Message-ID: <20150301.140545.1770896677577949653.davem@davemloft.net> (raw)
In-Reply-To: <cover.1425208501.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Sun, 1 Mar 2015 12:31:40 +0100
> This is the non-RFC version of my patchset posted before netdev01 [1]
> conference. It contains a couple of eBPF cleanups and preparation
> patches to get eBPF support into cls_bpf. The last patch adds the
> actual support. I'll post the iproute2 parts after the kernel bits
> are merged, an initial preview link to the code is mentioned in the
> last patch.
Series applied, thanks Daniel.
prev parent reply other threads:[~2015-03-01 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 11:31 [PATCH net-next v2 0/8] eBPF support for cls_bpf Daniel Borkmann
2015-03-01 11:31 ` [PATCH net-next v2 1/8] ebpf: remove kernel test stubs Daniel Borkmann
2015-03-01 11:31 ` [PATCH net-next v2 2/8] ebpf: constify various function pointer structs Daniel Borkmann
2015-03-01 11:31 ` [PATCH net-next v2 3/8] ebpf: export BPF_PSEUDO_MAP_FD to uapi Daniel Borkmann
2015-03-01 11:31 ` [PATCH net-next v2 4/8] ebpf: make internal bpf API independent of CONFIG_BPF_SYSCALL ifdefs Daniel Borkmann
2015-03-01 11:31 ` [PATCH net-next v2 5/8] ebpf: remove CONFIG_BPF_SYSCALL ifdefs in socket filter code Daniel Borkmann
2015-03-01 11:31 ` [PATCH net-next v2 6/8] ebpf: add sched_cls_type and map it to sk_filter's verifier ops Daniel Borkmann
2015-03-01 11:31 ` [PATCH net-next v2 7/8] ebpf: move read-only fields to bpf_prog and shrink bpf_prog_aux Daniel Borkmann
2015-03-01 11:31 ` [PATCH net-next v2 8/8] cls_bpf: add initial eBPF support for programmable classifiers Daniel Borkmann
2015-03-01 19:05 ` David Miller [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=20150301.140545.1770896677577949653.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.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).