On Dec 01, 2006 13:07 -0500, Trond Myklebust wrote: > > The more interesting case is multiple clients in the same directory. In > > order to provide strong consistency, both stat() and readdir() have to > > talk to the server (or more complicated leasing mechanisms are needed). > > Why would that be interesting? What applications do you have that > require strong consistency in that scenario? I keep looking for uses for > strong cache consistency with no synchronisation, but I have yet to meet > someone who has an actual application that relies on it.
To be honest, I can't think of any use that actually _requires_ consistency from stat() or readdir(), because even if the data was valid in the kernel at the time it was gathered, there is no guarantee all the files haven't been deleted by another thread even before the syscall is complete. Any pretending that the returned data is "current" is a pipe dream. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
