From 2e00a631e499e5674a05c1819a7a8f080ac802a5 Mon Sep 17 00:00:00 2001 From: Andrea Righi Date: Sat, 18 Oct 2008 20:27:13 -0700 Subject: [PATCH] --- yaml --- r: 115874 b: refs/heads/master c: 7a6560e02556b6f0a798c247f3a557c523d9701b h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/filesystems/proc.txt | 13 ++++++++----- 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/[refs] b/[refs] index 551d77a56294..92b68ae3bd23 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 9f1b16a51ea7180eca8a0d76a6bd587385a30757 +refs/heads/master: 7a6560e02556b6f0a798c247f3a557c523d9701b diff --git a/trunk/Documentation/filesystems/proc.txt b/trunk/Documentation/filesystems/proc.txt index 02cb7faeed6b..bcceb99b81dd 100644 --- a/trunk/Documentation/filesystems/proc.txt +++ b/trunk/Documentation/filesystems/proc.txt @@ -1384,15 +1384,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 -------------------------