From: Joe Stringer <joe@ovn.org>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org, wangnan0@huawei.com, ast@fb.com,
daniel@iogearbox.net, acme@kernel.org
Subject: [PATCHv2 perf/core 0/2] libbpf: Synchronize implementations
Date: Wed, 16 Nov 2016 09:43:22 -0800 [thread overview]
Message-ID: <20161116174324.29675-1-joe@ovn.org> (raw)
Update tools/lib/bpf to provide more functionality and improve interoperation
with other tools that generate and use eBPF code:
* The kernel uapi headers are a bit newer than the version in the tools/
directory; synchronize those.
* samples/bpf/libbpf* has a bit more functionality than tools/lib/bpf, so
extend tools/lib/bpf/bpf* with these functions to bring them into parity.
I've got a separate series to update samples/bpf/* to rely on these libraries,
but there's a conflict with davem's tree at the moment so I suppose that the
way forward is to get these patches through first, then take the samples
through net-next at a later time.
---
v2: Don't shift non-bpf code into libbpf.
Drop the patch to synchronize ELF definitions with tc.
v1: https://www.mail-archive.com/netdev@vger.kernel.org/msg135088.html
First post.
Joe Stringer (2):
tools lib bpf: Sync {tools,}/include/uapi/linux/bpf.h
tools lib bpf: Sync with samples/bpf/libbpf
tools/include/uapi/linux/bpf.h | 51 +++++++++++
tools/lib/bpf/bpf.c | 107 +++++++++++++++++-----
tools/lib/bpf/bpf.h | 202 +++++++++++++++++++++++++++++++++++++++--
tools/lib/bpf/libbpf.c | 3 +-
4 files changed, 330 insertions(+), 33 deletions(-)
--
2.9.3
next reply other threads:[~2016-11-16 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:43 Joe Stringer [this message]
2016-11-16 17:43 ` [PATCHv2 perf/core 1/2] tools lib bpf: Sync {tools,}/include/uapi/linux/bpf.h Joe Stringer
2016-11-17 1:28 ` Wangnan (F)
2016-11-16 17:43 ` [PATCHv2 perf/core 2/2] tools lib bpf: Sync with samples/bpf/libbpf Joe Stringer
2016-11-17 2:10 ` Wangnan (F)
2016-11-17 2:46 ` Joe Stringer
2016-11-17 3:21 ` Wangnan (F)
2016-11-17 3:40 ` Joe Stringer
2016-11-17 3:39 ` Wangnan (F)
2016-11-17 3:53 ` Joe Stringer
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=20161116174324.29675-1-joe@ovn.org \
--to=joe@ovn.org \
--cc=acme@kernel.org \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wangnan0@huawei.com \
/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).