On Thu, 12 Apr 2007, Dean Anderson wrote:
There may not be any degradation. The performance differences come if you have to replace every syscall with an open/ioctl/close cycle. This long cycle is only necessary if your syscall api can't muster a file discriptor and the open first/close last. However, I don't think afsd should have much problem with that. It seems easy enough to have a global file descriptor in the afsd, so that it doesn't need to open/close each time. The afsd can just open the driver once, and close it on exit. In that case, the overhead of a syscall is the same as ioctl. But it will change the internal afsd syscall api. It doesn't seem like changing that api would be a big deal. Is this more complex than it appears?
There are AFS syscall users besides afsd. fs is the obvious current one, but there are others present and more coming, and the one Tom alludes to will use it heavily.
_______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
