From: Greg KH <gregkh@linuxfoundation.org>
To: Luigi Rizzo <lrizzo@google.com>
Cc: linux-kernel@vger.kernel.org,
"Masami Hiramatsu" <mhiramat@kernel.org>,
akpm@linux-foundation.org, naveen.n.rao@linux.ibm.com,
ardb@kernel.org, "Luigi Rizzo" <rizzo@iet.unipi.it>,
"Paolo Abeni" <pabeni@redhat.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Jesper Dangaard Brouer" <hawk@kernel.org>
Subject: Re: [PATCH 0/2] quickstats, kernel sample collector
Date: Wed, 26 Feb 2020 11:14:49 +0100 [thread overview]
Message-ID: <20200226101449.GF127655@kroah.com> (raw)
In-Reply-To: <CAMOZA0+4Qg+bDQ1xGQ0jL=dvXK80LuxOa7tEd-=iBwat2M9pfg@mail.gmail.com>
On Wed, Feb 26, 2020 at 01:52:25AM -0800, Luigi Rizzo wrote:
> On Wed, Feb 26, 2020 at 12:10 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Feb 25, 2020 at 06:30:25PM -0800, Luigi Rizzo wrote:
> > > This patchset introduces a small library to collect per-cpu samples and
> > > accumulate distributions to be exported through debugfs.
> >
> > Shouldn't this be part of the tracing infrastructure instead of being
> > "stand-alone"?
>
> That's an option. My reasoning for making it standalone was that
> there are no dependencies in the (trivial) collection/aggregation part,
> so that code might conveniently replace/extend existing snippets of
> code that collect distributions in ad-hoc and perhaps suboptimal ways.
But that's what perf and tracing already does today, right? You need to
integrate into the existing subsystems of the kernel and not duplicate
things, creating new user/kernel apis whenever possible.
thanks,
greg k-h
next prev parent reply other threads:[~2020-02-26 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 2:30 [PATCH 0/2] quickstats, kernel sample collector Luigi Rizzo
2020-02-26 2:30 ` [PATCH 1/2] " Luigi Rizzo
2020-02-26 4:26 ` Randy Dunlap
2020-02-26 6:08 ` kbuild test robot
2020-02-26 8:12 ` Greg KH
2020-02-26 2:30 ` [PATCH 2/2] quickstats: user commands to trace execution time of code Luigi Rizzo
2020-02-26 8:10 ` [PATCH 0/2] quickstats, kernel sample collector Greg KH
2020-02-26 9:52 ` Luigi Rizzo
2020-02-26 10:14 ` Greg KH [this message]
2020-02-26 11:40 ` Luigi Rizzo
2020-02-26 16:57 ` Greg KH
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=20200226101449.GF127655@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=hawk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrizzo@google.com \
--cc=mhiramat@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=pabeni@redhat.com \
--cc=rizzo@iet.unipi.it \
--cc=toke@redhat.com \
/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