From: Namjae Jeon <namjae.j...@samsung.com>
This commit adds dirty_background_time description in bdi sysfs
documentation.
Signed-off-by: Namjae Jeon <namjae.j...@samsung.com>
Signed-off-by: Vivek Trivedi <t.vi...@samsung.com>
---
Documentation/ABI/testing/sysfs-class-bdi | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-bdi
b/Documentation/ABI/testing/sysfs-class-bdi
index 5f50097..018e26a 100644
--- a/Documentation/ABI/testing/sysfs-class-bdi
+++ b/Documentation/ABI/testing/sysfs-class-bdi
@@ -48,3 +48,16 @@ max_ratio (read-write)
most of the write-back cache. For example in case of an NFS
mount that is prone to get stuck, or a FUSE mount which cannot
be trusted to play fair.
+
+dirty_background_time (read-write)
+
+ It is used to start early writeback of given bdi once bdi dirty
+ data exceeds product of average write bandwidth and
+ dirty_background_time. It is mainly useful for tuning writeback
+ speed at 'NFS Server' so that NFS client could see better write speed.
+
+ However, sometimes it may not match user expectations as it is based
+ on bdi write bandwidth estimation. Write bandwidth estimation is a
+ best effort to estimate bdi write speed bandwidth. But it can be
+ wildly wrong in certain situations.
+ dirty_background_time is expressed in msec.
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
