LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* [PATCH] doc: add description to dirtytime_expire_seconds
@ 2018-05-30 23:56 Yang Shi
2018-06-15 0:23 ` Yang Shi
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Yang Shi @ 2018-05-30 23:56 UTC (permalink / raw)
To: tytso, corbet, akpm; +Cc: yang.shi, linux-fsdevel, linux-mm, linux-kernel
commit 1efff914afac8a965ad63817ecf8861a927c2ace ("fs: add
dirtytime_expire_seconds sysctl") introduced dirtytime_expire_seconds
knob, but there is not description about it in
Documentation/sysctl/vm.txt.
Add the description for it.
Cc: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Yang Shi <yang.shi@linux.alibaba.com>
---
I didn't dig into the old review discussion about why the description
was not added at the first place. I'm supposed every knob under /proc/sys
should have a brief description.
Documentation/sysctl/vm.txt | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
index 17256f2..f4f4f9c 100644
--- a/Documentation/sysctl/vm.txt
+++ b/Documentation/sysctl/vm.txt
@@ -27,6 +27,7 @@ Currently, these files are in /proc/sys/vm:
- dirty_bytes
- dirty_expire_centisecs
- dirty_ratio
+- dirtytime_expire_seconds
- dirty_writeback_centisecs
- drop_caches
- extfrag_threshold
@@ -178,6 +179,16 @@ The total available memory is not equal to total system memory.
==============================================================
+dirtytime_expire_seconds
+
+When a lazytime inode is constantly having its pages dirtied, it with an
+updated timestamp will never get chance to be written out. 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. It is expressed in seconds.
+
+==============================================================
+
dirty_writeback_centisecs
The kernel flusher threads will periodically wake up and write `old' data
--
1.8.3.1
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] doc: add description to dirtytime_expire_seconds
2018-05-30 23:56 [PATCH] doc: add description to dirtytime_expire_seconds Yang Shi
@ 2018-06-15 0:23 ` Yang Shi
2018-06-15 7:04 ` Nikolay Borisov
2018-06-26 14:34 ` Jonathan Corbet
2 siblings, 0 replies; 4+ messages in thread
From: Yang Shi @ 2018-06-15 0:23 UTC (permalink / raw)
To: tytso, corbet, akpm; +Cc: linux-fsdevel, linux-mm, linux-kernel
ping
Ted,
Any comment is appreciated.
Regards,
Yang
On 5/30/18 4:56 PM, Yang Shi wrote:
> commit 1efff914afac8a965ad63817ecf8861a927c2ace ("fs: add
> dirtytime_expire_seconds sysctl") introduced dirtytime_expire_seconds
> knob, but there is not description about it in
> Documentation/sysctl/vm.txt.
>
> Add the description for it.
>
> Cc: Theodore Ts'o <tytso@mit.edu>
> Signed-off-by: Yang Shi <yang.shi@linux.alibaba.com>
> ---
> I didn't dig into the old review discussion about why the description
> was not added at the first place. I'm supposed every knob under /proc/sys
> should have a brief description.
>
> Documentation/sysctl/vm.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
> index 17256f2..f4f4f9c 100644
> --- a/Documentation/sysctl/vm.txt
> +++ b/Documentation/sysctl/vm.txt
> @@ -27,6 +27,7 @@ Currently, these files are in /proc/sys/vm:
> - dirty_bytes
> - dirty_expire_centisecs
> - dirty_ratio
> +- dirtytime_expire_seconds
> - dirty_writeback_centisecs
> - drop_caches
> - extfrag_threshold
> @@ -178,6 +179,16 @@ The total available memory is not equal to total system memory.
>
> ==============================================================
>
> +dirtytime_expire_seconds
> +
> +When a lazytime inode is constantly having its pages dirtied, it with an
> +updated timestamp will never get chance to be written out. 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. It is expressed in seconds.
> +
> +==============================================================
> +
> dirty_writeback_centisecs
>
> The kernel flusher threads will periodically wake up and write `old' data
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] doc: add description to dirtytime_expire_seconds
2018-05-30 23:56 [PATCH] doc: add description to dirtytime_expire_seconds Yang Shi
2018-06-15 0:23 ` Yang Shi
@ 2018-06-15 7:04 ` Nikolay Borisov
2018-06-26 14:34 ` Jonathan Corbet
2 siblings, 0 replies; 4+ messages in thread
From: Nikolay Borisov @ 2018-06-15 7:04 UTC (permalink / raw)
To: Yang Shi, tytso, corbet, akpm; +Cc: linux-fsdevel, linux-mm, linux-kernel
On 31.05.2018 02:56, Yang Shi wrote:
> commit 1efff914afac8a965ad63817ecf8861a927c2ace ("fs: add
> dirtytime_expire_seconds sysctl") introduced dirtytime_expire_seconds
> knob, but there is not description about it in
> Documentation/sysctl/vm.txt.
>
> Add the description for it.
>
> Cc: Theodore Ts'o <tytso@mit.edu>
> Signed-off-by: Yang Shi <yang.shi@linux.alibaba.com>
> ---
> I didn't dig into the old review discussion about why the description
> was not added at the first place. I'm supposed every knob under /proc/sys
> should have a brief description.
>
> Documentation/sysctl/vm.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
> index 17256f2..f4f4f9c 100644
> --- a/Documentation/sysctl/vm.txt
> +++ b/Documentation/sysctl/vm.txt
> @@ -27,6 +27,7 @@ Currently, these files are in /proc/sys/vm:
> - dirty_bytes
> - dirty_expire_centisecs
> - dirty_ratio
> +- dirtytime_expire_seconds
> - dirty_writeback_centisecs
> - drop_caches
> - extfrag_threshold
> @@ -178,6 +179,16 @@ The total available memory is not equal to total system memory.
>
> ==============================================================
>
> +dirtytime_expire_seconds
> +
> +When a lazytime inode is constantly having its pages dirtied, it with an
The second part of this sentence, after the comma doesn't parse.
> +updated timestamp will never get chance to be written out. 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. It is expressed in seconds.
I think the final sentence is a bit redundant, given the very explicit
name of the knob.
> +
> +==============================================================
> +
> dirty_writeback_centisecs
>
> The kernel flusher threads will periodically wake up and write `old' data
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] doc: add description to dirtytime_expire_seconds
2018-05-30 23:56 [PATCH] doc: add description to dirtytime_expire_seconds Yang Shi
2018-06-15 0:23 ` Yang Shi
2018-06-15 7:04 ` Nikolay Borisov
@ 2018-06-26 14:34 ` Jonathan Corbet
2 siblings, 0 replies; 4+ messages in thread
From: Jonathan Corbet @ 2018-06-26 14:34 UTC (permalink / raw)
To: Yang Shi; +Cc: tytso, akpm, linux-fsdevel, linux-mm, linux-kernel
On Thu, 31 May 2018 07:56:53 +0800
Yang Shi <yang.shi@linux.alibaba.com> wrote:
> commit 1efff914afac8a965ad63817ecf8861a927c2ace ("fs: add
> dirtytime_expire_seconds sysctl") introduced dirtytime_expire_seconds
> knob, but there is not description about it in
> Documentation/sysctl/vm.txt.
>
> Add the description for it.
Applied to the docs tree, sorry for taking so long to get to it.
Thanks,
jon
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-06-26 14:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-30 23:56 [PATCH] doc: add description to dirtytime_expire_seconds Yang Shi
2018-06-15 0:23 ` Yang Shi
2018-06-15 7:04 ` Nikolay Borisov
2018-06-26 14:34 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).