From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: righi.andrea@gmail.com
Cc: kosaki.motohiro@jp.fujitsu.com,
Randy Dunlap <randy.dunlap@oracle.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Rubin <mrubin@google.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] documentation: clarify dirty_ratio and dirty_background_ratio description
Date: Thu, 9 Oct 2008 09:42:28 +0900 (JST) [thread overview]
Message-ID: <20081009094134.DEB8.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <48EC90EC.8060306@gmail.com>
> 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>
looks good to me.
> ---
> 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>
next prev parent reply other threads:[~2008-10-09 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 10:52 Andrea Righi
2008-10-09 0:42 ` KOSAKI Motohiro [this message]
2008-10-09 1:51 ` KAMEZAWA Hiroyuki
2008-10-09 7:32 ` Andrea Righi
2008-10-09 7:36 ` [PATCH] documentation: clarify dirty_ratio and dirty_background_ratio description (v2) Andrea Righi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081009094134.DEB8.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mrubin@google.com \
--cc=mtk.manpages@gmail.com \
--cc=peterz@infradead.org \
--cc=randy.dunlap@oracle.com \
--cc=righi.andrea@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox