On Jan 17, 2008, at 4:28 PM, Adam Leventhal wrote: > On Thu, Jan 17, 2008 at 04:17:25PM -0800, eric kustarz wrote: >> This is for just the NFSv3 server (as opposed to the client and >> server), right? > > Just the server. We have designs for client providers, but we > (obviously) > don't need them for Fishworks. > >> Any plans for the ancillary protocols of NFSv3 (NLM, MOUNT, stat, >> acl)? This would allow us to have a true "nfsv3_snoop.d". > > No immediate plans. What would be needed?
Same thing you did for NFSv4 and are doing for NFSv3 - mostly putting in some stable probes (like the DTRACE_NFSV4_2() calls in rfs4_op_*). The ACL server side code is at: http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/ common/fs/nfs/nfs_acl_srv.c The NLM code is under usr/closed. I'd have to dig for the stat and MOUNT stuff, but that might be trickier as i believe its in userland. Should be able to just check for callers of clnt_call(). The obvious big win is the provider for the NFSv3 protocol itself that you are doing. May want to garner interest from the community to see if anyone really cares about the other protocols. Nice to note that NFSv4 cleaned this up by only having one protocol. eric
