summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLaveesh Bansal <laveeshb@laveeshbansal.com>2026-01-06 14:50:59 +0000
committerChristian Brauner <brauner@kernel.org>2026-01-12 11:07:25 +0100
commit30ef9a20f1fdf6ab483d64fe3d54ba7d07b9b46f (patch)
tree963f1ef602c5429bd97e53a2a17fabc5c83798c7
parent543467d6fe97e27e22a26e367fda972dbefebbff (diff)
docs: clarify that dirtytime_expire_seconds=0 disables writeback
Document that setting vm.dirtytime_expire_seconds to zero disables periodic dirtytime writeback, matching the behavior of the related dirty_writeback_centisecs sysctl which already documents this. Signed-off-by: Laveesh Bansal <laveeshb@laveeshbansal.com> Link: https://patch.msgid.link/20260106145059.543282-3-laveeshb@laveeshbansal.com Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Christian Brauner <brauner@kernel.org>
-rw-r--r--Documentation/admin-guide/sysctl/vm.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/admin-guide/sysctl/vm.rst b/Documentation/admin-guide/sysctl/vm.rst
index 4d71211fdad8..e2fdbc521033 100644
--- a/Documentation/admin-guide/sysctl/vm.rst
+++ b/Documentation/admin-guide/sysctl/vm.rst
@@ -231,6 +231,8 @@ eventually gets pushed out to disk. This tunable is used to define when dirty
inode is old enough to be eligible for writeback by the kernel flusher threads.
And, it is also used as the interval to wakeup dirtytime_writeback thread.
+Setting this to zero disables periodic dirtytime writeback.
+
dirty_writeback_centisecs
=========================