Skip to content

Commit 30ef9a2

Browse files
laveeshbbrauner
authored andcommitted
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>
1 parent 543467d commit 30ef9a2

File tree

1 file changed

+2
-0
lines changed
  • Documentation/admin-guide/sysctl

1 file changed

+2
-0
lines changed

Documentation/admin-guide/sysctl/vm.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -231,6 +231,8 @@ eventually gets pushed out to disk. This tunable is used to define when dirty
231231
inode is old enough to be eligible for writeback by the kernel flusher threads.
232232
And, it is also used as the interval to wakeup dirtytime_writeback thread.
233233

234+
Setting this to zero disables periodic dirtytime writeback.
235+
234236

235237
dirty_writeback_centisecs
236238
=========================

0 commit comments

Comments
 (0)