On 16 Nov 2007, at 04:51, Spencer Shepler wrote:
Actually, the args/results have been extended in a way that it would appear as OPEN4args in both paths. So, yes, we could extend the proposed provided to accommodate NFSv4.1 with a method of communicating which minor version is being processed. Given the differences in the minor versions, I was thinking that a method that stood out more readily to the consumer of the provider would be helpful to alleviate confusion.
If I was dtracing an NFSv4 problem, I would at first not expect to have to differentiate between NFSv4.0 and NFSv4.1. Is this wrong? Are the two a completely different code path for the above mentioned open? I would be confused by different providers.
And a day earlier Adam wrote:
The plan is to have a different provider; either nfsv4c or nfsv4client or something.
I assume this is all talking about an NFS v4 server provider, guessing by the discussion and the FishWorks signature. Any NFS v4 client provider in sight? We have far more NFS clients than NFS servers to troubleshoot. Why would the nfsv4 client provider be called nfsv4c or nfsv4client, but the server just nfsv4? I would find that rather confusing as a user.
- mo
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dtrace-discuss mailing list [email protected]
