From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: [PATCH bpf-next 0/7] bpf: add perf event reading loop and move samples closer to libbpf Date: Fri, 11 May 2018 02:06:27 +0200 Message-ID: <5cb57ad9-445a-57d8-11ac-880975db68af@iogearbox.net> References: <20180510172443.17238-1-jakub.kicinski@netronome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: oss-drivers@netronome.com, netdev@vger.kernel.org To: Jakub Kicinski , alexei.starovoitov@gmail.com Return-path: Received: from www62.your-server.de ([213.133.104.62]:35609 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750722AbeEKAGa (ORCPT ); Thu, 10 May 2018 20:06:30 -0400 In-Reply-To: <20180510172443.17238-1-jakub.kicinski@netronome.com> Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: 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!