[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200226204954.vmhxd6d5utg63uet@ast-mbp>
Date: Wed, 26 Feb 2020 12:49:55 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Luigi Rizzo <lrizzo@...gle.com>
Cc: Toke Høiland-Jørgensen <toke@...hat.com>,
linux-kernel@...r.kernel.org,
Masami Hiramatsu <mhiramat@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg KH <gregkh@...uxfoundation.org>,
naveen.n.rao@...ux.ibm.com, ardb@...nel.org,
Luigi Rizzo <rizzo@....unipi.it>,
Paolo Abeni <pabeni@...hat.com>, giuseppe.lettieri@...pi.it,
Jesper Dangaard Brouer <hawk@...nel.org>, mingo@...hat.com,
acme@...nel.org, Steven Rostedt <rostedt@...dmis.org>,
peterz@...radead.org
Subject: Re: [PATCH v3 0/2] kstats: kernel metric collector
On Wed, Feb 26, 2020 at 09:26:22AM -0800, Luigi Rizzo wrote:
> Any pointers to this are welcome; Alexei mentioned fentry/fexit and
> bpf trampolines, but I haven't found an example that lets me do something
> equivalent to kretprobe (take a timestamp before and one after a function
> without explicit instrumentation)
please see the link in my previous email.
> - I still see some huge differences in usability, and this is in my opinion
> one very big difference between the two approaches. The systems where data
> collection may be of interest are not necessarily accessible to developers
> with the skills to write custom bpf code,
bpf code and tooling is already written. There are bcc and bpftrace scripts
that already do what you're proposing without adding any new code to the kernel.
These tools are trivial to use. Requires zero knowledge in bpf.
So please stop the fud.
Powered by blists - more mailing lists