From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: [PATCH v5 bpf-next 00/10] bpf, tracing: introduce bpf raw tracepoints Date: Mon, 26 Mar 2018 17:32:02 +0200 Message-ID: References: <20180324023038.938665-1-ast@fb.com> <20180326110435.4cdd7e7d@gandalf.local.home> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Alexei Starovoitov , davem@davemloft.net, torvalds@linux-foundation.org, peterz@infradead.org, netdev@vger.kernel.org, kernel-team@fb.com, linux-api@vger.kernel.org To: Steven Rostedt Return-path: Received: from www62.your-server.de ([213.133.104.62]:37738 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751995AbeCZPcL (ORCPT ); Mon, 26 Mar 2018 11:32:11 -0400 In-Reply-To: <20180326110435.4cdd7e7d@gandalf.local.home> Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 03/26/2018 05:04 PM, Steven Rostedt wrote: > On Mon, 26 Mar 2018 10:28:03 +0200 > Daniel Borkmann wrote: > >>> tracepoint base kprobe+bpf tracepoint+bpf raw_tracepoint+bpf >>> task_rename 1.1M 769K 947K 1.0M >>> urandom_read 789K 697K 750K 755K >> >> Applied to bpf-next, thanks Alexei! > > Please wait till you have the proper acks. Some of this affects > tracing. Ok, I thought time up to v5 was long enough. Anyway, in case there are objections I can still toss out the series from bpf-next tree worst case should e.g. follow-up fixups not be appropriate. Thanks, Daniel