2010/9/9 Steve French <smfrench@xxxxxxxxx>: > Note that metadata caching is common for most network file systems > (not unique to cifs or nfs) - and is usually done on a timer. > > NFSv3 data caching is unsafe - no guarantees data makes it to server > until sync or close. Generally if a file has not changed between > close and open - seems reasonable to keep the cached copy. If we As I mentioned in the first email, CIFS servers doesn't update mtime of a file every time and that brings complexity. So we can't be sure that we have actual data of a file in a cache. > have two opens of the same file from different clients we won't be > caching anyway. But now CIFS kernel client does it - it uses cache. As for SMB2 - it's the same. > > In SMB2 we will be doing batch oplock. > -- Best regards, Pavel Shilovsky. -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
