On Tue, 6 Oct 2009, Peter Staubach wrote: > > Three operations are implemented by the new XATTR protocol and map to > > syscalls: > > > > - GETXATTR getxattr(2) > > - LISTXTTR listxattr(2) > > - SETXATTR setxattr(2) and removexattr(2) > > > > This code passes basic testing of the above syscalls, although there are > > some areas which still need work: > > > > Is there a set of tests which are used to test this functionality? No, I just manually run a set of commands to verify basic behavior. I gather LTP would be the best place to add tests for this? > > - Interoperability with other OSs (we probably should at least > > discuss with BSD folk) > > > > It would be good to include the BSD folks, but I think that more > valuable targets would be those with volume servers that might be > encountered at customer sites. I think that we need NetApp, EMC, > perhaps Sun, providing some feedback on the protocol and semantics. Given that IETF activity is closed for v3, I wonder what the best forum would be to reach all these folk? > > - Caching of xattrs at the client > > > > This will need a closer specification for the semantics associated > with these xattrs. The need will be how to determine when to > invalidate cached xattrs. I suspect user namespace xattrs should be treated like file data wrt caching (i.e. they're fully under the control of the user). > On more bullet that I might suggest is ensuring that the protocol > is compliant with the RPC and XDR standards. Thanks, I'll check that. - James -- James Morris <jmorris@xxxxxxxxx> -- 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
