From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Luigi Rizzo <lrizzo@google.com>,
linux-kernel@vger.kernel.org, mhiramat@kernel.org,
akpm@linux-foundation.org, gregkh@linuxfoundation.org,
naveen.n.rao@linux.ibm.com, ardb@kernel.org, rizzo@iet.unipi.it,
pabeni@redhat.com, giuseppe.lettieri@unipi.it, hawk@kernel.org,
mingo@redhat.com, acme@kernel.org, rostedt@goodmis.org,
peterz@infradead.org
Cc: Luigi Rizzo <lrizzo@google.com>
Subject: Re: [PATCH v3 0/2] kstats: kernel metric collector
Date: Wed, 26 Feb 2020 16:00:49 +0100 [thread overview]
Message-ID: <87ftexz93y.fsf@toke.dk> (raw)
In-Reply-To: <20200226135027.34538-1-lrizzo@google.com>
Luigi Rizzo <lrizzo@google.com> writes:
> This patchset introduces a small library to collect per-cpu samples and
> accumulate distributions to be exported through debugfs.
>
> This v3 series addresses some initial comments (mostly style fixes in the
> code) and revises commit logs.
Could you please add a proper changelog spanning all versions of the
patch as you iterate?
As for the idea itself; picking up this argument you made on v1:
> The tracepoint/kprobe/kretprobe solution is much more expensive --
> from my measurements, the hooks that invoke the various handlers take
> ~250ns with hot cache, 1500+ns with cold cache, and tracing an empty
> function this way reports 90ns with hot cache, 500ns with cold cache.
I think it would be good if you could include an equivalent BPF-based
implementation of your instrumentation example so people can (a) see the
difference for themselves and get a better idea of how the approaches
differ in a concrete case and (b) quantify the difference in performance
between the two implementations.
-Toke
next prev parent reply other threads:[~2020-02-26 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 13:50 [PATCH v3 0/2] kstats: kernel metric collector Luigi Rizzo
2020-02-26 13:50 ` [PATCH v3 1/2] " Luigi Rizzo
2020-02-26 14:48 ` Paolo Abeni
2020-03-10 13:58 ` kbuild test robot
2020-03-10 16:44 ` kbuild test robot
2020-03-11 0:08 ` kbuild test robot
2020-03-11 3:30 ` kbuild test robot
2020-02-26 13:50 ` [PATCH v3 2/2] kstats: kretprobe and tracepoint support Luigi Rizzo
2020-02-26 15:00 ` Toke Høiland-Jørgensen [this message]
2020-02-26 16:31 ` [PATCH v3 0/2] kstats: kernel metric collector Alexei Starovoitov
2020-02-26 17:26 ` Luigi Rizzo
2020-02-26 19:14 ` Peter Zijlstra
2020-02-26 20:49 ` Alexei Starovoitov
2020-02-26 23:11 ` Toke Høiland-Jørgensen
2020-02-27 10:31 ` Luigi Rizzo
2020-02-27 12:13 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftexz93y.fsf@toke.dk \
--to=toke@redhat.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=giuseppe.lettieri@unipi.it \
--cc=gregkh@linuxfoundation.org \
--cc=hawk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrizzo@google.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=rizzo@iet.unipi.it \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox