aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorGravatar Nikolaus Rath <Nikolaus@rath.org>2016-11-10 14:04:51 -0800
committerGravatar Nikolaus Rath <Nikolaus@rath.org>2016-11-10 14:04:51 -0800
commitc95846bcc6a7ff30642694445d0bd8523f9056eb (patch)
tree200ce3515a52045d083bbb5c1bc22f2b53869f3a /include
parent0e08174044cca6578eb2d39ccb8c0f829e95a97c (diff)
Improve documentation of fuse_conn_info.time_gran.
Fixes #97.
Diffstat (limited to 'include')
-rw-r--r--include/fuse_common.h15
1 files changed, 12 insertions, 3 deletions
diff --git a/include/fuse_common.h b/include/fuse_common.h
index 44b0634..2ba3888 100644
--- a/include/fuse_common.h
+++ b/include/fuse_common.h
@@ -259,15 +259,24 @@ struct fuse_conn_info {
unsigned max_background;
/**
+
* Kernel congestion threshold parameter
*/
unsigned congestion_threshold;
/**
- * Time granularity if kernel is responsible for setting times (in nsec)
+ * When FUSE_CAP_WRITEBACK_CACHE is enabled, the kernel is responsible
+ * for updating mtime and ctime when write requests are received. The
+ * updated values are passed to the filesystem with setattr() requests.
+ * However, if the filesystem does not support the full resolution of
+ * the kernel timestamps (nanoseconds), the mtime and ctime values used
+ * by kernel and filesystem will differ (and result in an apparent
+ * change of times after a cache flush).
*
- * Should be power of 10. A zero (default) value is equivalent to
- * 1000000000 (1sec).
+ * To prevent this problem, this variable can be used to inform the
+ * kernel about the timestamp granularity supported by the file-system.
+ * The value should be power of 10. A zero (default) value is
+ * equivalent to 1000000000 (1sec).
*/
unsigned time_gran;