Displaying 20 results from an estimated 9000 matches similar to: "Code Review for NFS v3 client DTrace provider"
2008 Nov 17
0
Overhead evaluation of my nfsv3client probe implementation
Hi,
Thanks for the comment for my nfsv3client probe implementation! I have made changes accordingly.
Webrev: http://cr.opensolaris.org/~danhua/webrev/
To reduce the overhead, I use a local variable to save XID, rather than
alloc memory space with kmem_zalloc().
According to the overhead caused by tsd_get() and tsd_set(), I did an
experiment to measure it.
In this experiment, I run a dtrace
2008 Sep 10
1
Proposal for DTrace probes for NFS v3 client
Hi,
This is a proposal for probes for NFS v3 client(see attachment). These
probes are under a new DTrace provider: nfsv3client. These new probes
support tracing NFS v3 client activities such as sending RPC requests to
NFS v3 server and receiving RPC replies from NFS v3 server. Formats and
arguments of these new probes are quite similar to existing NFS v3
probes on server side (provider: nfsv3).
2008 Oct 30
7
Is there any way to check if DTrace is running or a DTrace probe is enabled?
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
2009 Nov 06
7
Status of DTrace NFSv3/v4 client providers
We recently had a strange NFS performance anomaly between a V880 running
snv_124 and two NetApp filers. To investigate, a DTrace NFSv4 (and
eventually NFSv3) client provider would been extremely helpful.
Unfortunately, all I could find were a request for code review of a v3
client provider and another request for help developing a v4 provider.
Nothing seems to have come from those initiatives,
2009 Apr 23
1
Dtrace provider for the COMSTAR iscsi Target Port Provider - Review Request
The iscsit_dtrace_draftv5.txt describes the Dtrace probes definition for
the COMSTAR iSCSI target port provider. For all those interested in
iSCSI, please take a look and send me your
feedback/questions/suggestions etc by Thursday, April 20, 2009
thanks
Priya
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: iscsit_dtrace_draftv5.txt
URL:
2010 Mar 22
1
TCP and UDP DTrace provider specifications for review
hi folks
we''re in final approach with Brendan''s work on
the TCP and UDP providers, which have been
discussed here previously in the context of the
overall networking provider plan at:
http://hub.opensolaris.org/bin/view/Community+Group+dtrace/NetworkProvider
The specs have been updated to reflect recent
changes and are available for review here:
2009 Apr 29
2
DTrace provider proposal: fibre channel (fc) COMSTAR port provider probes
I have added a specification of probes for the fibre channel COMSTAR
port provider to the DTrace section of wikis.sun.com. The proposal may
be found here: http://wikis.sun.com/display/DTrace/fibre+channel+Provider
I welcome feedback regarding this proposal.
Thanks,
Sam
2008 Apr 01
10
Request for code review: the brendan() action
This came up as an RFE during the conference (I believe it''s been logged
as "4012008: brendan() action needed for DTrace Toolkit".)
As everyone here is aware, DTrace is not quite as user friendly as it
could be. For the uninitiated, it can be confusing to run a DTrace
script and not see the expected output. Brendan Gregg has addressed
this in the DTrace Toolkit[1] by
2007 Dec 22
3
Erlang DTrace Provider
DTrace folks,
I''m pleased to introduce a potential new DTrace-sponsored project: the
Erlang DTrace provider. To be good OpenSolaris citizens, we want to put
the formation of this officially sponsored project to a vote -- as outlined
in the OpenSolaris Constitution -- so here are the details for the new
Project, as prepared by the Project Team:
Name : Erlang DTrace Integration
2009 Apr 30
0
DTrace provider proposal: COMSTAR iSCSI target port provider probes
I would like to request approval of the the DTrace proposal for the COMSTAR
iSCSI target port provider. I have updated the specification of the
iscsi provider at http://wikis.sun.com/display/DTrace/iscsi+Provider. Your
feedback is appreciated.
thanks
Priya
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: iscsit_dtrace_draftv8.txt
URL:
2007 Oct 29
2
autoconf test for building dtrace USDT probes?
X.Org has adopted GNU autoconf as its build configuration mechanism,
so when I integrated the dtrace probes, I checked to see if they
should be built using this test, checking for the existence of a
program named "dtrace" in the path:
dnl Check for dtrace program (needed to build Xserver dtrace probes)
AC_ARG_WITH(dtrace, AS_HELP_STRING([--with-dtrace=PATH],
[Enable dtrace
2009 Apr 29
0
COMSTAR iscsi DTrace Probes -
The earlier post with the Dtrace probes definition (sent on April 23) was only to solicit feedback from all prospective users of iSCSI DTrace probes. I will follow up shortly with an updated document requesting approval from the community.
thanks
Priya
-------- Original Message --------
Subject: Dtrace provider for the COMSTAR iscsi Target Port Provider -
Review Request
Date: Thu, 23 Apr
2009 Apr 17
4
unable to find any probes from the nfs provider
I want to list/use the nfs probes but I get the error "dtrace: failed to
match nfs*:::: No probe matches description". Is there a way to enable
nfs provider probes? My system is running snv_112 (bfu''ed from the gate
archive)
# dtrace -lP nfs*
ID PROVIDER MODULE FUNCTION NAME
dtrace: failed to match nfs*:::: No probe matches
2007 Dec 20
6
DTrace IP provider, step 1
G''Day All,
I''m putting together a PSARC case to begin integration of the DTrace network
providers. I''ve drawn up a rough plan which splits this project into over a
dozen smaller steps, as documented on the network provider page:
http://www.opensolaris.org/os/community/dtrace/NetworkProvider#Plan
Below is a draft PSARC document for task 1, IP provider send/receive
2007 Sep 01
1
Hekp dtrace -l is bleeding Unstable implementation details all over my USDT probe namespace :(
Hi,
As I''ve discussed before whenever we add USDT probes to a C++ function
and call dtrace -l we get the mangled C++ name for the dtrace function,
being listed :(
Now the point of USDT probes is to abstract a higher level semantic
construct for users to make use of. Surely it is not meant to be listing
Unstable Interfaces (implementation details), such as the containing C++
2008 Dec 04
2
Round four: Re: code review req: 6750659 drti.o crashes app due to corrupt environment
I believe that I have incorporated all of the feedback given
(thanks!). Changes since the 2008-11-16 version include:
- ksh style & coding standards compliance in test script (Roland)
- "dof_init_debug == B_FALSE" vs. "!dof_init_debug" (Adam)
The updated webrev is at:
http://cr.opensolaris.org/~mgerdts/6750659-2008-12-03/
--
Mike Gerdts
http://mgerdts.blogspot.com/
2006 Sep 21
1
Dtrace script compilation error.
Hi All,
One of the customer is seeing the following error messages.
He is using a S10U1 system with all latest patches.
Dtrace script is attached.
I am not seeing these error messages on S10U2 system.
What could be the problem?
Thanks,
Gangadhar.
------------------------------------------------------------------------
rroberto at njengsunu60-2:~$ dtrace -AFs /lib/svc/share/kcfd.d
dtrace:
2008 Feb 26
4
Why dtrace doesn''t work on some workstation?
Dtrace does work on some workstation, such as as follows,
-----------------------------------------------------------
bash-3.00# dtrace -s ./mem.d `pgrep test`
dtrace: script ''./mem.d'' matched 5 probes
^C
bash-3.00# uname -a
SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100
bash-3.00# dtrace -V
dtrace: Sun D 1.1
2007 Aug 14
8
sh DTrace provider available
As noted on my blog and at
http://www.opensolaris.org/os/community/dtrace/shells/ I''ve made
available a DTrace provider for the Bourne shell. Before anyone starts
yelling at me for not starting with another shell, read the blog I made
explaining why we started with shell (link on the community page
referenced above).
For /bin/sh, I''ve put up something akin to a chapter in
2008 May 16
1
Question about dtrace -G -s x.d
Hi,
I''m wondering about what dtrace -G -s probes.d code.o is doing.
Does this command change the code.o object file or is it only
creating an probes.o
object file. I''m wondering how I can gather many dtrace probes from many
different directories in one provider to see if this is possible.
Rgrds Mikael