mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryan Cantrill <bmc@zion.eng.sun.com>
To: lkml-7994@mc.frodoid.org (Julien Oster)
Cc: kloczek@rudy.mif.pg.gda.pl, usenet-20040502@usenet.frodoid.org,
	miles.lane@comcast.net, linux-kernel@vger.kernel.org,
	bmc@kiowa.eng.sun.com
Subject: Re: DTrace-like analysis possible with future Linux kernels?
Date: Sat, 21 Aug 2004 14:49:18 -0700 (PDT)	[thread overview]
Message-ID: <200408212149.i7LLnIeu144328@zion.eng.sun.com> (raw)
In-Reply-To: <87d61k4rmr.fsf@killer.ninja.frodoid.org> from Julien Oster at "Aug 21, 2004 02:12:12 pm"


> > PS. Very interesting commens about this thread is on Bryan Cantrill
> > (DTrace developer) blog:
> > http://blogs.sun.com/roller/page/bmc/20040820#dtrace_on_lkml
> > Bryan blog is also yet another Dtrace knowledge source ..
> 
> Oh, yeah, great. A whole blog entry dedicated to me. Now I am a moron,
> absolutely clueless and I am "looking to confirm preconceived notions
> rather than understand new technology".
> 
> Sorry, but that goes a little too far. No, I didn't try out dtrace
> and, right after reading the article (and that's the important thing!)
> I didn't seek for further information about it, I'm not a Solaris
> System Administrator right now (I was, some years ago). And all I was
> saying is that this *article* was just ridiculous.

As a reminder, you _didn't_ read the entire article, by your own admission:

  That article is way too hypey...  I couldn't even read it completely,
  it was just too much.

And that was actually my point:  you spent more time denigrating the article
for lack of supporting detail than it would have taken you to _finish_ the
article and discover those supporting details.  

> But in that article, I was just missing the objectiveness. A quick
> note about the fact that Sun's been introducing dtrace for Solaris 10
> and what it is, what it does, would have been much better instead of
> talking about a "Cantrill explosion", how "DTrace has completely
> changed the way I do business" (actual quotes).

You don't like customer quotes?  It seems to me that quotes like that
one (or like the other customer quotes that appear in the article)
give weight to the claims.  Don't you like to hear from people who have
actually _used_ a technology?  I know that I do -- those who have used
a technology are likely to have a much more balanced view on its
strengths and weaknesses than those who have just read about it.  (Indeed,
this is true of pretty much anything -- experience matters.)

> Florian and Alan told me in a quick and objective manner why dtrace is
> a good thing, and I am glad for that information. I never stated that
> DTrace was a bad thing. 

Oh really?  You wrote:

  Come on, it's profiling. As presented by that article, it is even more
  micro optimization than one would think. What with tweaking the disk
  I/O improvements and all... If my harddisk accesses were a microsecond
  more immediate or my filesystem giving a quantum more transfer rate,
  it would be nice, but I certainly wouldn't get enthusiastic and I bet
  nobody would even notice.

So come on, yourself:  it's _not_ just "profiling" and DTrace finds
problems that are _much_ larger than "micro-optimizations" (indeed, that's
the whole damn point), and finishing the article would have told you that.

> Bryan Cantrill, I can understand that you have to defend DTrace. But
> please, PLEASE stop saying that I am a clueless moron if I wasn't even
> ranting about you, ranting about DTrace, but just about *that single
> article* and it's presentation of DTrace to me.

You were attacking more than just the article; you ended with:

  I sure hope that article is meant sarcastically. By the way, did I
  miss something or is profiling suddenly a new thing again?

You asked if you were missing something, and I replied that you were
missing plenty.  Presumably you now feel informed (if a little embarrassed),
and I think that those that you misinformed also now realize that what
you provided them was misinformation.  So as far as I'm concerned, that's
the end of that.

	- Bryan

--------------------------------------------------------------------------
Bryan Cantrill, Solaris Kernel Development.       http://blogs.sun.com/bmc

  parent reply	other threads:[~2004-08-21 21:52 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 22:22 Miles Lane
2004-08-19 23:01 ` Karim Yaghmour
2004-08-19 23:23 ` Julien Oster
2004-08-19 22:33   ` Alan Cox
2004-08-20 10:08     ` Alex Bennee
2004-08-20 11:21       ` Robert Schwebel
2004-08-20  0:23   ` Florian Weimer
2004-08-20 13:34     ` Alexander Nyberg
2004-08-20 13:46       ` Florian Weimer
2004-08-20 16:46         ` David S. Miller
2004-08-21  6:03   ` Tomasz Kłoczko
2004-08-21  6:12     ` David S. Miller
2004-08-21  6:22       ` Tomasz Kłoczko
2004-08-21 12:12     ` Julien Oster
2004-08-21 13:27       ` Tomasz Kłoczko
2004-08-21 21:49       ` Bryan Cantrill [this message]
2004-08-23 23:08         ` Christoph Halder
2004-08-22 11:35     ` Alan Cox
2004-08-22 18:27       ` Tomasz Kłoczko
2004-08-22 18:46         ` Alan Cox
2004-08-23 17:34           ` Tomasz Kłoczko
2004-08-22 23:03         ` John Levon
2004-08-23 19:48       ` Robert Milkowski
2004-08-24  0:39         ` David S. Miller
2004-08-28 19:16         ` Alan Cox
2004-08-29  0:14           ` Tomasz Kłoczko
2004-08-29  5:30             ` David S. Miller
2004-08-29 10:45               ` Tomasz Kłoczko
2004-08-29 17:46                 ` David S. Miller
2004-08-29 10:53               ` Robert Milkowski
2004-08-29 10:29           ` Robert Milkowski
2004-08-31 20:16   ` Timothy Miller
     [not found] <2ptdY-42Y-55@gated-at.bofh.it>
     [not found] ` <2uPdM-380-11@gated-at.bofh.it>
     [not found]   ` <2uUwL-6VP-11@gated-at.bofh.it>
     [not found]     ` <2uWfh-8jo-29@gated-at.bofh.it>
     [not found]       ` <2uXl0-Gt-27@gated-at.bofh.it>
     [not found]         ` <2vge2-63k-15@gated-at.bofh.it>
     [not found]           ` <2vgQF-6Ai-39@gated-at.bofh.it>
     [not found]             ` <2vipq-7O8-15@gated-at.bofh.it>
     [not found]               ` <2vj2b-8md-9@gated-at.bofh.it>
     [not found]                 ` <2vDtS-bq-19@gated-at.bofh.it>
2004-08-21 15:01                   ` PATCH: cdrecord: avoiding scsi device numbering for ide devices Pascal Schmidt
2004-08-21 15:57                     ` Joerg Schilling
2004-08-22 11:56                       ` Joerg Schilling
2004-08-22 13:13                         ` Pascal Schmidt
2004-08-22 16:00                           ` Christer Weinigel
2004-08-22 16:32                             ` Joerg Schilling
2004-08-22 17:18                               ` Christer Weinigel
2004-08-22 19:22                                 ` DTrace-like analysis possible with future Linux kernels? Joerg Schilling
2004-08-22 19:26                             ` PATCH: cdrecord: avoiding scsi device numbering for ide devices Tonnerre
2004-08-22 20:14                               ` DTrace-like analysis possible with future Linux kernels? Joerg Schilling
2004-08-22 20:33                                 ` Tonnerre
2004-08-22 20:38                                   ` Alan Cox
2004-08-22 20:43                                   ` Joerg Schilling
2004-08-22 21:37                                     ` Christer Weinigel
2004-08-23 11:44                                       ` Joerg Schilling
2004-08-23 17:40                                 ` Horst von Brand
     [not found] <2v3Ad-5tc-29@gated-at.bofh.it>
     [not found] ` <2v4w9-6aQ-5@gated-at.bofh.it>
     [not found]   ` <2vxeJ-4kg-3@gated-at.bofh.it>
     [not found]     ` <2vZNN-7AT-33@gated-at.bofh.it>
     [not found]       ` <2w5q4-34M-1@gated-at.bofh.it>
     [not found]         ` <2w9Dq-65C-13@gated-at.bofh.it>
2004-08-23 18:19           ` Andi Kleen
2004-08-24  4:14 Joerg Schilling
2004-08-28 19:15 ` Alan Cox
     [not found] <2wAWW-12a-11@gated-at.bofh.it>
2004-08-24 13:04 ` Pascal Schmidt
2004-08-24 13:07   ` Joerg Schilling

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=200408212149.i7LLnIeu144328@zion.eng.sun.com \
    --to=bmc@zion.eng.sun.com \
    --cc=bmc@kiowa.eng.sun.com \
    --cc=kloczek@rudy.mif.pg.gda.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml-7994@mc.frodoid.org \
    --cc=miles.lane@comcast.net \
    --cc=usenet-20040502@usenet.frodoid.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

all inboxes | Powered by JetHome®