public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Julien Oster <usenet-20040502@usenet.frodoid.org>
Cc: Miles Lane <miles.lane@comcast.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DTrace-like analysis possible with future Linux kernels?
Date: Thu, 19 Aug 2004 23:33:45 +0100	[thread overview]
Message-ID: <1092954824.28931.9.camel@localhost.localdomain> (raw)
In-Reply-To: <87hdqyogp4.fsf@killer.ninja.frodoid.org>

On Gwe, 2004-08-20 at 00:23, Julien Oster 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.

Yes and no. LTT is just profiling too. Both of them are making people
notice because they allow that system profiling work to be done by 
two-banana grade operations staff not by the company wizard.

Neither are perfect - users want a "why is it going slow button"
with a "make it work" and "beat the crap out of the user who caused it"
option set.

"Profiling for the people" as it were.. (as opposed to the current
fad of 'profiling the people')

Alan


  reply	other threads:[~2004-08-19 23:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 22:22 DTrace-like analysis possible with future Linux kernels? Miles Lane
2004-08-19 23:01 ` Karim Yaghmour
2004-08-19 23:23 ` Julien Oster
2004-08-19 22:33   ` Alan Cox [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
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=1092954824.28931.9.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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