From: "Takashi Nishiie" <t-nishiie@np.css.fujitsu.com>
To: <fox@crisp.demon.co.uk>, <bart.vanassche@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: dtrace for linux
Date: Fri, 25 Apr 2008 17:03:11 +0900 [thread overview]
Message-ID: <000e01c8a6aa$ce638960$6b2a9c20$@css.fujitsu.com> (raw)
In-Reply-To: <200804211958.m3LJw6QM004827@crisp.demon.co.uk>
>> On Sun, Apr 20, 2008 at 1:17 AM, <fox@crisp.demon.co.uk> wrote:
>>>
>>> I would like to announce that I am working on dtrace for Linux.
>>> I have the userland dtrace binary compiled, along with the first
>>> pre-pre-alpha dtracedrv.ko module loaded into my kernel.
>>
>> This is great news. How will this dtrace implementation differ from
>> SystemTap (http://sourceware.org/systemtap/) ?
>>
>> Bart.
>>
>>
>
>Hello Bart,
>
>
>I dont know systemtap all that well, other than what i have
>read on the net and browsed in the source. systemtap is similar,
>but dtrace provides a high level functional language (D) and
>a set of methodologies and scripts which mean learning/training
>will make it easier to use.
Hello,
SystemTAP is the tool developed in order to do the same thing
as Dtrace. When development of SystemTAP started, Dtrace was not
able to be used with restriction by the license at linux. The
difference in both SystemTAP and Dtrace is produced by avoiding
being based on mounting peculiar to linux, and a license.
By the way, aren't any ideas found in order to mitigate the
load when acquiring trace? If load when having taken trace as
for LTTng as for SystemTAP is too heavy, I feel. For example,
it is desirable that trace with lighter load can be taken by the
limiting conditions of obtaining the trace result only for
several seconds until panic occurs.
Regards
next prev parent reply other threads:[~2008-04-25 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 19:58 dtrace for linux paul
2008-04-25 8:03 ` Takashi Nishiie [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-25 23:05 fox
2008-04-25 23:05 paul
2008-04-21 19:59 fox
2008-04-21 19:59 paul
2008-04-21 19:58 fox
2008-04-20 0:13 paul
2008-04-21 9:29 ` Jiri Kosina
2008-04-19 23:17 fox
2008-04-21 10:22 ` Bart Van Assche
2006-03-29 6:14 DTrace for Linux Tushar
2006-03-29 6:52 ` Randy.Dunlap
2006-03-30 20:55 ` Valerie Henson
2006-03-31 0:43 ` Frank Ch. Eigler
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='000e01c8a6aa$ce638960$6b2a9c20$@css.fujitsu.com' \
--to=t-nishiie@np.css.fujitsu.com \
--cc=bart.vanassche@gmail.com \
--cc=fox@crisp.demon.co.uk \
--cc=linux-kernel@vger.kernel.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