From: Daniel Borkmann <daniel@iogearbox.net>
To: stephen@networkplumber.org
Cc: ast@kernel.org, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH iproute2 -master 0/4] Minor BPF updates on frontend
Date: Tue, 2 Feb 2016 01:12:25 +0100 [thread overview]
Message-ID: <cover.1454370543.git.daniel@iogearbox.net> (raw)
Couple of minor updates on tc frontend.
Stephen, the patches are against iproute2 -master branch and *on top of*
the two that are already lingering in patchwork:
- http://patchwork.ozlabs.org/patch/569923/
- http://patchwork.ozlabs.org/patch/571385/
Thanks!
Daniel Borkmann (4):
tc, bpf, examples: further bpf_api improvements
tc, bpf: improve verifier logging
tc, bpf: give some more hints wrt false relos
tc, bpf: use bind/type macros from gelf
examples/bpf/bpf_cyclic.c | 4 +-
examples/bpf/bpf_graft.c | 13 +---
examples/bpf/bpf_prog.c | 26 +++----
examples/bpf/bpf_shared.c | 3 +-
examples/bpf/bpf_tailcall.c | 12 +--
include/bpf_api.h | 56 ++++++++++++--
tc/tc_bpf.c | 173 +++++++++++++++++++++++++++++++-------------
tc/tc_bpf.h | 1 -
8 files changed, 191 insertions(+), 97 deletions(-)
--
1.9.3
next reply other threads:[~2016-02-02 0:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 0:12 Daniel Borkmann [this message]
2016-02-02 0:12 ` [PATCH iproute2 -master 1/4] tc, bpf, examples: further bpf_api improvements Daniel Borkmann
2016-02-02 0:12 ` [PATCH iproute2 -master 2/4] tc, bpf: improve verifier logging Daniel Borkmann
2016-02-02 0:51 ` John Fastabend
2016-02-02 5:02 ` Stephen Hemminger
2016-02-02 0:12 ` [PATCH iproute2 -master 3/4] tc, bpf: give some more hints wrt false relos Daniel Borkmann
2016-02-02 0:12 ` [PATCH iproute2 -master 4/4] tc, bpf: use bind/type macros from gelf Daniel Borkmann
2016-02-02 5:07 ` [PATCH iproute2 -master 0/4] Minor BPF updates on frontend Stephen Hemminger
2016-02-02 9:22 ` Daniel Borkmann
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=cover.1454370543.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).