Trond Myklebust wrote: > On Thu, 2009-01-22 at 08:07 -0500, Steve Dickson wrote: >>> I think it might be a good idea to flesh out a bit what you mean by >>> "debugging" here. Since you mentioned it in conjunction with the two >>> words "administrators" and "scripts", I assume that you are not talking >>> about kernel code debugging? >> I'm talking debugging for both admins and kernel people... >> >> With trace points and systemtap you can do both. > > Yes, but we still need to figure out details of what each type of user > is expecting/wants. Will that be possible? Until we get something in their hands, how will they even know what they want or need. > > I suspect that when we get down to cases, we will find that a lot of the > tracepoints that administrators find useful will want to be put in the > VFS rather than in the filesystems themselves. If you have tracepoints > in sys_stat() and sys_fstat(), why would you also need a tracepoint in > nfs_getattr()? AFAICS, that would just make scripting ugly... I believe there is an effort to do some type of system call tracing as we speak and that effort should be followed to ensure there is no duplicate of effort... But in the end, I would think more would be better then less... since each point can be explicitly enabled and disabled a little duplication may not be all that bad.. steved. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
