[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <lzbix55ms6mxta5xf4yvkr66qhxnomqc34diinzqrfluvr2xd7@vnzhyi5r44qe>
Date: Tue, 6 Jan 2026 10:37:09 +0100
From: Jan Kara <jack@...e.cz>
To: Laveesh Bansal <laveeshb@...eeshbansal.com>
Cc: viro@...iv.linux.org.uk, brauner@...nel.org, jack@...e.cz,
tytso@....edu, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] docs: clarify that dirtytime_expire_seconds=0
disables writeback
On Fri 02-01-26 20:16:57, Laveesh Bansal wrote:
> 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>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@...e.cz>
Honza
> ---
> 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
>
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists