mdb's dtrace* dcmds may be of assistance...
> ::dtrace_state
ADDR MINOR PROC NAME FILE
ffffff02d485e280 2 ffffff02b2a45570 dtrace ffffff02cc672d58
> ::dcmds ! grep dtr
dtrace - print dtrace(1M)-like output
dtrace_aggstat - print DTrace aggregation hash statistics
dtrace_dynstat - print DTrace dynamic variable hash statistics
dtrace_errhash - print DTrace error hash
dtrace_helptrace - print DTrace helper trace
dtrace_state - print active DTrace consumers
id2probe - translate a dtrace_id_t to a dtrace_probe_t
I'm sure others will be able to give you more interesting stuff, but
this might be a start...
Nathan.
On 31/10/08 09:28 AM, Danhua Shao wrote:
> Hi,
>
> I am adding DTrace probes within NFS v3 client. In my current
> implementation, I use some tsd_*() functions and kmem_zalloc() function.
> These functions might be heavy and affect the performance. I want to
> call this function only when DTrace is running or the DTrace probes are
> enable. So is there a way to check DTrace is running or DTrace probe is
> enabled?
>
> Regards,
>
> Danhua
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss@opensolaris.org
--
//////////////////////////////////////////////////////////////////
// Nathan Kroenert [EMAIL PROTECTED] //
// Senior Systems Engineer Phone: +61 3 9869 6255 //
// Global Systems Engineering Fax: +61 3 9869 6288 //
// Level 7, 476 St. Kilda Road //
// Melbourne 3004 Victoria Australia //
//////////////////////////////////////////////////////////////////
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
