From: Stephen Hemminger <stephen@networkplumber.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -next v2 5/5] {f,m}_bpf: add more example code
Date: Sun, 29 Nov 2015 11:56:01 -0800 [thread overview]
Message-ID: <20151129115601.76c07295@xeon-e3> (raw)
In-Reply-To: <d40d1f8668201d9a766aabef4045c6baf14aa146.1448547199.git.daniel@iogearbox.net>
On Thu, 26 Nov 2015 15:38:46 +0100
Daniel Borkmann <daniel@iogearbox.net> wrote:
> I've added three examples to examples/bpf/ that demonstrate how one can
> implement eBPF tail calls in tc with f.e. multiple levels of nesting.
> That should act as a good starting point, but also as test cases for the
> ELF loader and kernel. A real test suite for {f,m,e}_bpf is still to be
> developed in future work.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Acked-by: Alexei Starovoitov <ast@kernel.org>
All applied to net-next branch.
prev parent reply other threads:[~2015-11-29 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 14:38 [PATCH iproute2 -next v2 0/5] BPF updates Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 1/5] {f,m}_bpf: make tail calls working Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 2/5] {f,m}_bpf: check map attributes when fetching as pinned Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 3/5] {f,m}_bpf: allow for user-defined object pinnings Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 4/5] {f,m}_bpf: allow updates on program arrays Daniel Borkmann
2015-11-26 15:19 ` Hannes Frederic Sowa
2015-11-26 15:51 ` Daniel Borkmann
2015-11-26 14:38 ` [PATCH iproute2 -next v2 5/5] {f,m}_bpf: add more example code Daniel Borkmann
2015-11-29 19:56 ` Stephen Hemminger [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=20151129115601.76c07295@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=ast@kernel.org \
--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).