Commit a1299792 authored by Kirill Smelkov's avatar Kirill Smelkov

.

parent 36766e1d
...@@ -20,7 +20,7 @@ we have to disable FUSE_AUTO_INVAL_DATA to tell the kernel we are fully ...@@ -20,7 +20,7 @@ we have to disable FUSE_AUTO_INVAL_DATA to tell the kernel we are fully
responsible for invalidating pagecache. If we don't, the kernel will be responsible for invalidating pagecache. If we don't, the kernel will be
clearing whole cache of head/file on e.g. its mtime change. clearing whole cache of head/file on e.g. its mtime change.
Note: FUSE_AUTO_INVAL_DATA does not fully prevent kernel from automatically Note: disabling FUSE_AUTO_INVAL_DATA does not fully prevent kernel from automatically
invalidating pagecache - e.g. it will invalidate whole cache on file size changes: invalidating pagecache - e.g. it will invalidate whole cache on file size changes:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/fuse/inode.c?id=e0bc833d10#n233 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/fuse/inode.c?id=e0bc833d10#n233
......
...@@ -96,12 +96,12 @@ ...@@ -96,12 +96,12 @@
// In order to support isolation, wcfs implements isolation protocol that // In order to support isolation, wcfs implements isolation protocol that
// must be cooperatively followed by both wcfs and client. // must be cooperatively followed by both wcfs and client.
// //
// First, client mmaps latest bigfile, but does not access it // First, client mmaps latest bigfile, but does not access it:
// //
// mmap(head/bigfile/<bigfileX>) // mmap(head/bigfile/<bigfileX>)
// //
// Then client opens head/watch and tells wcfs through it for which ZODB state // Then client opens head/watch and tells wcfs through it for which ZODB state
// it wants to get bigfile's view. // it wants to get bigfile's view:
// //
// C: 1 watch <bigfileX> @<at> // C: 1 watch <bigfileX> @<at>
// //
...@@ -168,7 +168,7 @@ ...@@ -168,7 +168,7 @@
// A single client can send several watch requests through single head/watch // A single client can send several watch requests through single head/watch
// open, as well as it can use several head/watch opens simultaneously. // open, as well as it can use several head/watch opens simultaneously.
// The server sends pin notifications for all files requested to be watched via // The server sends pin notifications for all files requested to be watched via
// every head/watch open. // every opened head/watch link.
// //
// Note: a client could use a single watch to manage its several views for the same // Note: a client could use a single watch to manage its several views for the same
// file but with different <at>. This could be achieved via watching with // file but with different <at>. This could be achieved via watching with
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment