Hi, Adam and Robert, Thanks for your comments. I will work out new probes under the *current* NFSv4 provider - nfsv4. For the different implementations to same operation in version 4 and version 4.1, developers can find the differences according to the function names in the full probe names: nfsv4::rfs4_op_*:op_* or nfsv4::mds_op_*:op_*
Regards, Danhua Adam Leventhal wrote: >>> I am working on adding new DTrace probes for operations NFSv4.1 and >>> am confused about setup their provider: Add all new probes into a >>> new provider for NFSv4.1 or add them into the current NFSv4.0 >>> provider? >>> >> Since protocol state is separate between 40 and 41 my preference would >> be the second >> solution, *but* then i'm a developer.. and that is my main focus right >> now.. as an end-user >> wanting to know basic v4 information (which clients, which files, IO >> performance), i don't care about this silly minor version thing.. >> >> The 4.1 code is in flux; but i would recommend that the existing NFSv4 >> probes be placed in the corresponding mds_op* functions. > > I'd argue that from the customer perspective, having a single provider > would be simpler. Perhaps it would be a good idea to design a proposal > for the putative new provider as well as the augmentations to the exsting > one. > > Adam > > -- > Adam Leventhal, Fishworks http://blogs.sun.com/ahl >
