[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5cb57ad9-445a-57d8-11ac-880975db68af@iogearbox.net>
Date: Fri, 11 May 2018 02:06:27 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>,
alexei.starovoitov@...il.com
Cc: oss-drivers@...ronome.com, netdev@...r.kernel.org
Subject: Re: [PATCH bpf-next 0/7] bpf: add perf event reading loop and move
samples closer to libbpf
On 05/10/2018 07:24 PM, Jakub Kicinski wrote:
> Hi!
>
> 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.
Looks good, applied to bpf-next, thanks Jakub!
Powered by blists - more mailing lists