[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba96cda5-c4d6-4d66-0128-b7053d25fcd8@iogearbox.net>
Date: Mon, 26 Mar 2018 17:32:02 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Alexei Starovoitov <ast@...com>, davem@...emloft.net,
torvalds@...ux-foundation.org, peterz@...radead.org,
netdev@...r.kernel.org, kernel-team@...com,
linux-api@...r.kernel.org
Subject: Re: [PATCH v5 bpf-next 00/10] bpf, tracing: introduce bpf raw
tracepoints
On 03/26/2018 05:04 PM, Steven Rostedt wrote:
> On Mon, 26 Mar 2018 10:28:03 +0200
> Daniel Borkmann <daniel@...earbox.net> 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
Powered by blists - more mailing lists