From: Yonghong Song <yhs@fb.com>
To: <netdev@vger.kernel.org>
Cc: Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>,
Yonghong Song <yhs@fb.com>
Subject: [PATCH bpf-next 0/2] tools/bpf: expose several libbpf API functions
Date: Mon, 4 Feb 2019 11:00:57 -0800 [thread overview]
Message-ID: <20190204190057.3965903-1-yhs@fb.com> (raw)
This patch set exposed a few functions in libbpf.
All these newly added API functions are helpful for
JIT based bpf compilation where .BTF and .BTF.ext
are available as in-memory data blobs.
Patch #1 exposed several btf_ext__* API functions which
are used to handle .BTF.ext ELF sections.
Patch #2 refactored the function bpf_map_find_btf_info()
and exposed API function btf__get_map_kv_tids() to
retrieve the map key/value type id's generated by
bpf program through BPF_ANNOTATE_KV_PAIR macro.
Yonghong Song (2):
tools/bpf: expose functions btf_ext__* as API functions
tools/bpf: implement libbpf btf__get_map_kv_tids() API function
tools/lib/bpf/btf.c | 73 ++++++++++++++++++++++++++++++++++++++++
tools/lib/bpf/btf.h | 28 ++++++++-------
tools/lib/bpf/libbpf.c | 72 +++++----------------------------------
tools/lib/bpf/libbpf.map | 7 ++++
4 files changed, 105 insertions(+), 75 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-04 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 19:00 Yonghong Song [this message]
2019-02-04 19:00 ` [PATCH bpf-next 1/2] tools/bpf: expose functions btf_ext__* as API functions Yonghong Song
2019-02-04 19:00 ` [PATCH bpf-next 2/2] tools/bpf: implement libbpf btf__get_map_kv_tids() API function Yonghong Song
2019-02-04 20:51 ` [PATCH bpf-next 0/2] tools/bpf: expose several libbpf API functions Alexei Starovoitov
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=20190204190057.3965903-1-yhs@fb.com \
--to=yhs@fb.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--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