This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Sorry for the delayed response... That darn flux capacitor broke again! ;-)
Chuck Lever wrote:
I'm all for improving the observability of the NFS client.Well, in theory, trace points will also touch the server and all of the rpc code...
But I don't (yet) see the advantage of adding this complexity in the
mount path. Maybe the more complex and asynchronous parts of the NFS
client, like the cached read and write paths, are more suitable to this
type of tool.Well the complexity is, at this point, due to how the trace points are tied to and used by the systemtap. I'm hopeful this complexity will die down as time goes on...
Why can't we simply improve the information content of the dprintks?The theory is trace point can be turned on, in production kernels, with
little or no performance issues...
Can you give a few real examples of problems that these new trace pointsThey can supply more information that can be used by both a kernel
can identify that better dprintks wouldn't be able to address?
guy and an IT guy.... Meaning they can supply detailed structure information
that a kernel guy would need as well as supplying the simple error code
that an IT guy would be interested.
Generally, what kind of problems do admins face that the dprintks don'tNot being an admin guy, I really don't have an answer for this... but
handle today, and what are the alternatives to addressing those issues?
I can say since trace point are not so much of a drag on the system as
printks are.. with in timing issues using trace point would be a big advantage
over printks
Do admins who run enterprise kernels actually use SystemTap, or do theyCurrently to run systemtap, one need kernel debug info and kernel developer
fall back on network traces and other tried and true troubleshooting
methodologies?
info installed on the system. Most productions system don't install those types
of packages.... But with trace points those type of packages will no longer be
needed, so I could definitely see admins using systemtap once its available...
Look at Dtrace... people are using that now that its available and fairly stable.
If we think the mount path needs such instrumentation, consider updating
fs/nfs/mount_clnt.c and net/sunrpc/rpcb_clnt.c as well.
I was just following what what was currently being debug when 'rpcinfo -m nfs -s mount' was set...
-- Chuck Lever chuck[dot]lever[at]oracle[dot]com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |