> If we have a purely Linux-specific hack to ensure cache coherency, > that will still corrupt the cache on those *NIX clients that use > ordinary cache coherency checking (i.e. checking mtime + file size) > rather than cache invalidation. Its what Solaris implements and what SunOS back down to 3.x implements. I wouldnt be suprised if others do likewise ? > It also avoids a lot of unnecessary cache flushing. Imagine having to > reread your entire mailbox every time you open the file whether or not > a new message has arrived. Ugh... Interesting point. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- NFS locking bug -- limited mtime resolution means nfs... Trond Myklebust
- Re: NFS locking bug -- limited mtime resolution ... Alan Cox
- Re: NFS locking bug -- limited mtime resolut... Trond Myklebust
- Re: NFS locking bug -- limited mtime res... Alan Cox
- Re: NFS locking bug -- limited mtime res... Jeff Epler
- Re: NFS locking bug -- limited mtime... Trond Myklebust
- Re: NFS locking bug -- limited mtime... Trond Myklebust
- Re: NFS locking bug -- limited ... Jeff Epler
- Re: NFS locking bug -- limited mtime res... Andi Kleen
- Re: NFS locking bug -- limited mtime... Trond Myklebust
- Re: NFS locking bug -- limited ... Andi Kleen
- Re: NFS locking bug -- limited ... Frank van Maarseveen
- Re: NFS locking bug -- limited mtime... Jeff Epler
- Re: NFS locking bug -- limited mtime resolution ... Jeff Epler