[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260106145059.543282-3-laveeshb@laveeshbansal.com>
Date: Tue, 6 Jan 2026 14:50:59 +0000
From: Laveesh Bansal <laveeshb@...eeshbansal.com>
To: viro@...iv.linux.org.uk,
brauner@...nel.org
Cc: jack@...e.cz,
tytso@....edu,
linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
stable@...r.kernel.org,
Laveesh Bansal <laveeshb@...eeshbansal.com>
Subject: [PATCH v2 2/2] 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@...eeshbansal.com>
Reviewed-by: Jan Kara <jack@...e.cz>
---
Documentation/admin-guide/sysctl/vm.rst | 2 ++
1 file changed, 2 insertions(+)
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
=========================
--
2.43.0
Powered by blists - more mailing lists