From: "Iruata Souza" <iru.muzgo@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] crosstool fails on gentoo
Date: Mon, 2 Jun 2008 21:50:53 -0300 [thread overview]
Message-ID: <d1c554290806021750j880083h5461f449e94152c9@mail.gmail.com> (raw)
In-Reply-To: <13426df10806021621m7fc4a26fg42b0e8e112837402@mail.gmail.com>
On Mon, Jun 2, 2008 at 8:21 PM, ron minnich <rminnich@gmail.com> wrote:
> On Mon, Jun 2, 2008 at 4:00 PM, Iruata Souza <iru.muzgo@gmail.com> wrote:
>
>> I don't have any solaris boxes to play now, but I remember when taking
>> a dtrace course - more or less two years ago - that I managed to see
>> the performance of a nice machine go down only by setting all it's
>> tracing points. I know that this could be considered normal if it
>> wasn't for the fact that, with two xterms opened, the one which
>> started dtrace, after a series of ^C, had 'transfered' to it the
>> command-line history of the other xterm. It was a peculiar situation
>> since the instructor was telling us about the non-intrusiveness of the
>> tool.
>>
>
> it's worth reading the papers. Dtrace is quite capable.
>
> But look at the issues. You are taking a piece of code and splicing in
> another piece of code. It can get fun. What if someone was running the
> code you are splicing (think: SMP). What about time to remove it: make
> sure that (a) nobody is running the spliced in code (how do you do
> that in the general case) and (b) nobody is trying to run where you
> are putting the code back. What if the original code had an INT
> instruction? What if it tickled an IRQ? What if code you spliced in
> takes a fault?
>
> Check out the kprobes device in linux to see how nasty it can get.
>
> At the same time, people delivering software to end users make good
> use of dtrace, so it's kind of hard to fault Sun for putting it in
> there -- they do have paychecks to hand out. And I expect that lots of
> customers demand that it stay in there ...
>
just like many people, I have made good use of dtrace myself. but the
need for a tool like that seems to me one more evidence of the trend
in talk about in your first post. in the pile of layers one has to dig
to find/fix/rework something, sometimes dtrace seems like the better -
or even the only one at hand - thing to deal with it.
put short: dtrace-like tools are good but, in general, having the need
for it is not.
iru
next prev parent reply other threads:[~2008-06-03 0:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <483D8DBE.4090005@cableone.net>
[not found] ` <200805282337.11349.yann.morin.1998@anciens.enib.fr>
2008-06-01 15:12 ` Enrico Weigelt
2008-06-02 19:25 ` Uriel
2008-06-02 19:55 ` ron minnich
2008-06-02 19:57 ` erik quanstrom
2008-06-02 20:09 ` Eric Van Hensbergen
2008-06-02 20:37 ` Uriel
2008-06-02 20:45 ` erik quanstrom
2008-06-02 21:00 ` Uriel
2008-06-02 22:32 ` Roman Shaposhnik
2008-06-02 23:00 ` Iruata Souza
2008-06-02 23:21 ` ron minnich
2008-06-03 0:50 ` Iruata Souza [this message]
2008-06-03 0:54 ` erik quanstrom
2008-06-03 2:02 ` Nick LaForge
2008-06-05 11:11 ` Enrico Weigelt
2008-06-05 11:21 ` Bruce Ellis
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=d1c554290806021750j880083h5461f449e94152c9@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=9fans@9fans.net \
/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).