diff options
author | Daniel Borkmann <daniel@iogearbox.net> | 2018-05-11 01:48:19 +0200 |
---|---|---|
committer | Daniel Borkmann <daniel@iogearbox.net> | 2018-05-11 01:48:32 +0200 |
commit | a84880ef4352c61896028448d809e32f8646628d (patch) | |
tree | 880940e6af0c8352acc8c5f2158ec1457a2dc08c /init | |
parent | cb9c28ef579debbc51e48b37f2534390f5da8467 (diff) | |
parent | be5bca44aa6b37b88e900d5f5f155911d6984d86 (diff) | |
download | linux-a84880ef4352c61896028448d809e32f8646628d.tar.gz linux-a84880ef4352c61896028448d809e32f8646628d.tar.bz2 linux-a84880ef4352c61896028448d809e32f8646628d.zip |
Merge branch 'bpf-perf-rb-libbpf'
Jakub Kicinski says:
====================
This series started out as a follow up to the bpftool perf event dumping
patches.
As suggested by Daniel patch 1 makes use of PERF_SAMPLE_TIME to simplify
code and improve accuracy of timestamps.
Remaining patches are trying to move perf event loop into libbpf as
suggested by Alexei. One user for this new function is bpftool which
links with libbpf nicely, the other, unfortunately, is in samples/bpf.
Remaining patches make samples/bpf link against full libbpf.a (not just
a handful of objects). Once we have full power of libbpf at our disposal
we can convert some of XDP samples to use libbpf loader instead of
bpf_load.c. My understanding is that this is the desired direction,
at least for networking code.
====================
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions