On Nov 19, 2007, at 5:34 PM, Moritz Willers wrote: > > 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.
As you note, .0 and .1 are minor versions of the overall NFSv4 protocol. Unfortuntaely, that english description hides the impact of the additional operations in 4.1 and the fact that the Sessions related functionality is "mandatory to implement" in the minor version. The other thing to note is that protocol state from one minor version (namely filehandles) can not be used in one of the other minor versions. So, it turns out that clients will make a choice of minor version for a mount and stick to it; just as they do today with NFSv3 and NFSv4. This behavior is likely more to the point. Spencer _______________________________________________ dtrace-discuss mailing list [email protected]
