bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: brendan.d.gregg@gmail.com
Cc: kris.van.hees@oracle.com, daniel@iogearbox.net, corbet@lwn.net,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	dtrace-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
	rostedt@goodmis.org, mhiramat@kernel.org, acme@kernel.org,
	ast@kernel.org, peterz@infradead.org, clm@fb.com
Subject: Re: [PATCH V2 1/1 (was 0/1 by accident)] tools/dtrace: initial implementation of DTrace
Date: Wed, 10 Jul 2019 15:31:16 -0700 (PDT)	[thread overview]
Message-ID: <20190710.153116.614111233846989165.davem@davemloft.net> (raw)
In-Reply-To: <CAE40pdeSVN+QhhUeQ4sEbsyzJ+NWkQA5XU5X0FrKAbRMHPzBsw@mail.gmail.com>

From: Brendan Gregg <brendan.d.gregg@gmail.com>
Date: Wed, 10 Jul 2019 14:49:52 -0700

> Hey Kris -- so you're referring to me, and I've used DTrace more than
> anyone over the past 15 years, and I don't think anyone has used all
> the different Linux tracers more than I have. I think my opinion has a
> lot of value.

+1

I seriously am against starting to merge all of these userland tracing
tools into the tree.

They belong as separate independant projects, outside of the kernel
tree.

  reply	other threads:[~2019-07-10 22:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 15:37 [PATCH V2 0/1] tools/dtrace: initial implementation of DTrace Kris Van Hees
2019-07-10 15:42 ` Kris Van Hees
2019-07-10 18:12   ` [PATCH V2 1/1 (was 0/1 by accident)] " Kris Van Hees
2019-07-10 19:32     ` Daniel Borkmann
2019-07-10 19:47       ` Steven Rostedt
2019-07-10 20:30       ` Jonathan Corbet
2019-07-10 21:19         ` Daniel Borkmann
2019-07-10 21:36           ` Kris Van Hees
2019-07-10 21:49             ` Brendan Gregg
2019-07-10 22:31               ` David Miller [this message]
2019-07-10 21:35         ` Brendan Gregg
2019-07-10 22:32 ` [PATCH V2 0/1] " David Miller

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=20190710.153116.614111233846989165.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=acme@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brendan.d.gregg@gmail.com \
    --cc=clm@fb.com \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=kris.van.hees@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).