* Re: [PATCH] documentation: clarify dirty_ratio and dirty_background_ratio description
@ 2008-10-09 1:51 ` KAMEZAWA Hiroyuki
0 siblings, 0 replies; 10+ messages in thread
From: KAMEZAWA Hiroyuki @ 2008-10-09 1:51 UTC (permalink / raw)
To: righi.andrea
Cc: Randy Dunlap, Michael Kerrisk, Peter Zijlstra, Andrew Morton,
Michael Rubin, KOSAKI Motohiro, linux-mm, LKML
On Wed, 08 Oct 2008 12:52:28 +0200
Andrea Righi <righi.andrea@gmail.com> wrote:
> The current documentation of dirty_ratio and dirty_background_ratio is a
> bit misleading.
>
> In the documentation we say that they are "a percentage of total system
> memory", but the current page writeback policy, intead, is to apply the
> percentages to the dirtyable memory, that means free pages + reclaimable
> pages.
>
Right.
> Better to be more explicit to clarify this concept.
>
> Signed-off-by: Andrea Righi <righi.andrea@gmail.com>
But I wonder "reclaimable memory" seems to be a difficult word for users....
"free pages + mapped pages + file cache, not including locked page and HugePage"
?
Anyway,
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> Documentation/filesystems/proc.txt | 11 ++++++-----
> 1 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
> index f566ad9..be69c8b 100644
> --- a/Documentation/filesystems/proc.txt
> +++ b/Documentation/filesystems/proc.txt
> @@ -1380,15 +1380,16 @@ causes the kernel to prefer to reclaim dentries and inodes.
> dirty_background_ratio
> ----------------------
>
> -Contains, as a percentage of total system memory, the number of pages at which
> -the pdflush background writeback daemon will start writing out dirty data.
> +Contains, as a percentage of the dirtyable system memory (free pages +
> +reclaimable pages), the number of pages at which the pdflush background
> +writeback daemon will start writing out dirty data.
>
> dirty_ratio
> -----------------
>
> -Contains, as a percentage of total system memory, the number of pages at which
> -a process which is generating disk writes will itself start writing out dirty
> -data.
> +Contains, as a percentage of the dirtyable system memory (free pages +
> +reclaimable pages), the number of pages at which a process which is generating
> +disk writes will itself start writing out dirty data.
>
> dirty_writeback_centisecs
> -------------------------
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] documentation: clarify dirty_ratio and dirty_background_ratio description
2008-10-09 1:51 ` KAMEZAWA Hiroyuki
@ 2008-10-09 7:32 ` Andrea Righi
-1 siblings, 0 replies; 10+ messages in thread
From: Andrea Righi @ 2008-10-09 7:32 UTC (permalink / raw)
To: KAMEZAWA Hiroyuki
Cc: Randy Dunlap, Michael Kerrisk, Peter Zijlstra, Andrew Morton,
Michael Rubin, KOSAKI Motohiro, linux-mm, LKML
KAMEZAWA Hiroyuki wrote:
> On Wed, 08 Oct 2008 12:52:28 +0200
> Andrea Righi <righi.andrea@gmail.com> wrote:
>
>> The current documentation of dirty_ratio and dirty_background_ratio is a
>> bit misleading.
>>
>> In the documentation we say that they are "a percentage of total system
>> memory", but the current page writeback policy, intead, is to apply the
>> percentages to the dirtyable memory, that means free pages + reclaimable
>> pages.
>>
> Right.
>
>> Better to be more explicit to clarify this concept.
>>
>> Signed-off-by: Andrea Righi <righi.andrea@gmail.com>
>
> But I wonder "reclaimable memory" seems to be a difficult word for users....
>
> "free pages + mapped pages + file cache, not including locked page and HugePage"
> ?
> Anyway,
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Sounds better. I'll add these details and post a new patch.
Thanks,
-Andrea
>
>> ---
>> Documentation/filesystems/proc.txt | 11 ++++++-----
>> 1 files changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
>> index f566ad9..be69c8b 100644
>> --- a/Documentation/filesystems/proc.txt
>> +++ b/Documentation/filesystems/proc.txt
>> @@ -1380,15 +1380,16 @@ causes the kernel to prefer to reclaim dentries and inodes.
>> dirty_background_ratio
>> ----------------------
>>
>> -Contains, as a percentage of total system memory, the number of pages at which
>> -the pdflush background writeback daemon will start writing out dirty data.
>> +Contains, as a percentage of the dirtyable system memory (free pages +
>> +reclaimable pages), the number of pages at which the pdflush background
>> +writeback daemon will start writing out dirty data.
>>
>> dirty_ratio
>> -----------------
>>
>> -Contains, as a percentage of total system memory, the number of pages at which
>> -a process which is generating disk writes will itself start writing out dirty
>> -data.
>> +Contains, as a percentage of the dirtyable system memory (free pages +
>> +reclaimable pages), the number of pages at which a process which is generating
>> +disk writes will itself start writing out dirty data.
>>
>> dirty_writeback_centisecs
>> -------------------------
>>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] documentation: clarify dirty_ratio and dirty_background_ratio description
@ 2008-10-09 7:32 ` Andrea Righi
0 siblings, 0 replies; 10+ messages in thread
From: Andrea Righi @ 2008-10-09 7:32 UTC (permalink / raw)
To: KAMEZAWA Hiroyuki
Cc: Randy Dunlap, Michael Kerrisk, Peter Zijlstra, Andrew Morton,
Michael Rubin, KOSAKI Motohiro, linux-mm, LKML
KAMEZAWA Hiroyuki wrote:
> On Wed, 08 Oct 2008 12:52:28 +0200
> Andrea Righi <righi.andrea@gmail.com> wrote:
>
>> The current documentation of dirty_ratio and dirty_background_ratio is a
>> bit misleading.
>>
>> In the documentation we say that they are "a percentage of total system
>> memory", but the current page writeback policy, intead, is to apply the
>> percentages to the dirtyable memory, that means free pages + reclaimable
>> pages.
>>
> Right.
>
>> Better to be more explicit to clarify this concept.
>>
>> Signed-off-by: Andrea Righi <righi.andrea@gmail.com>
>
> But I wonder "reclaimable memory" seems to be a difficult word for users....
>
> "free pages + mapped pages + file cache, not including locked page and HugePage"
> ?
> Anyway,
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Sounds better. I'll add these details and post a new patch.
Thanks,
-Andrea
>
>> ---
>> Documentation/filesystems/proc.txt | 11 ++++++-----
>> 1 files changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
>> index f566ad9..be69c8b 100644
>> --- a/Documentation/filesystems/proc.txt
>> +++ b/Documentation/filesystems/proc.txt
>> @@ -1380,15 +1380,16 @@ causes the kernel to prefer to reclaim dentries and inodes.
>> dirty_background_ratio
>> ----------------------
>>
>> -Contains, as a percentage of total system memory, the number of pages at which
>> -the pdflush background writeback daemon will start writing out dirty data.
>> +Contains, as a percentage of the dirtyable system memory (free pages +
>> +reclaimable pages), the number of pages at which the pdflush background
>> +writeback daemon will start writing out dirty data.
>>
>> dirty_ratio
>> -----------------
>>
>> -Contains, as a percentage of total system memory, the number of pages at which
>> -a process which is generating disk writes will itself start writing out dirty
>> -data.
>> +Contains, as a percentage of the dirtyable system memory (free pages +
>> +reclaimable pages), the number of pages at which a process which is generating
>> +disk writes will itself start writing out dirty data.
>>
>> dirty_writeback_centisecs
>> -------------------------
>>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH] documentation: clarify dirty_ratio and dirty_background_ratio description (v2)
2008-10-09 1:51 ` KAMEZAWA Hiroyuki
@ 2008-10-09 7:36 ` Andrea Righi
-1 siblings, 0 replies; 10+ messages in thread
From: Andrea Righi @ 2008-10-09 7:36 UTC (permalink / raw)
To: Randy Dunlap, Michael Kerrisk
Cc: KAMEZAWA Hiroyuki, Peter Zijlstra, Andrew Morton, Michael Rubin,
KOSAKI Motohiro, linux-mm, LKML
The current documentation of dirty_ratio and dirty_background_ratio is a
bit misleading.
In the documentation we say that they are "a percentage of total system
memory", but the current page writeback policy, intead, is to apply the
percentages to the dirtyable memory, that means free pages + reclaimable
pages.
Better to be more explicit to clarify this concept.
Signed-off-by: Andrea Righi <righi.andrea@gmail.com>
Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
---
Documentation/filesystems/proc.txt | 13 ++++++++-----
1 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
index 394eb2c..474bf8b 100644
--- a/Documentation/filesystems/proc.txt
+++ b/Documentation/filesystems/proc.txt
@@ -1380,15 +1380,18 @@ causes the kernel to prefer to reclaim dentries and inodes.
dirty_background_ratio
----------------------
-Contains, as a percentage of total system memory, the number of pages at which
-the pdflush background writeback daemon will start writing out dirty data.
+Contains, as a percentage of the dirtyable system memory (free pages + mapped
+pages + file cache, not including locked pages and HugePages), the number of
+pages at which the pdflush background writeback daemon will start writing out
+dirty data.
dirty_ratio
-----------------
-Contains, as a percentage of total system memory, the number of pages at which
-a process which is generating disk writes will itself start writing out dirty
-data.
+Contains, as a percentage of the dirtyable system memory (free pages + mapped
+pages + file cache, not including locked pages and HugePages), the number of
+pages at which a process which is generating disk writes will itself start
+writing out dirty data.
dirty_writeback_centisecs
-------------------------
^ permalink raw reply related [flat|nested] 10+ messages in thread
* [PATCH] documentation: clarify dirty_ratio and dirty_background_ratio description (v2)
@ 2008-10-09 7:36 ` Andrea Righi
0 siblings, 0 replies; 10+ messages in thread
From: Andrea Righi @ 2008-10-09 7:36 UTC (permalink / raw)
To: Randy Dunlap, Michael Kerrisk
Cc: KAMEZAWA Hiroyuki, Peter Zijlstra, Andrew Morton, Michael Rubin,
KOSAKI Motohiro, linux-mm, LKML
The current documentation of dirty_ratio and dirty_background_ratio is a
bit misleading.
In the documentation we say that they are "a percentage of total system
memory", but the current page writeback policy, intead, is to apply the
percentages to the dirtyable memory, that means free pages + reclaimable
pages.
Better to be more explicit to clarify this concept.
Signed-off-by: Andrea Righi <righi.andrea@gmail.com>
Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
---
Documentation/filesystems/proc.txt | 13 ++++++++-----
1 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
index 394eb2c..474bf8b 100644
--- a/Documentation/filesystems/proc.txt
+++ b/Documentation/filesystems/proc.txt
@@ -1380,15 +1380,18 @@ causes the kernel to prefer to reclaim dentries and inodes.
dirty_background_ratio
----------------------
-Contains, as a percentage of total system memory, the number of pages at which
-the pdflush background writeback daemon will start writing out dirty data.
+Contains, as a percentage of the dirtyable system memory (free pages + mapped
+pages + file cache, not including locked pages and HugePages), the number of
+pages at which the pdflush background writeback daemon will start writing out
+dirty data.
dirty_ratio
-----------------
-Contains, as a percentage of total system memory, the number of pages at which
-a process which is generating disk writes will itself start writing out dirty
-data.
+Contains, as a percentage of the dirtyable system memory (free pages + mapped
+pages + file cache, not including locked pages and HugePages), the number of
+pages at which a process which is generating disk writes will itself start
+writing out dirty data.
dirty_writeback_centisecs
-------------------------
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply related [flat|nested] 10+ messages in thread