From: Randy Dunlap <rdunlap@infradead.org>
To: poros@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
trivial@kernel.org
Subject: Re: [PATCH] Documentation: incorrect formula to calculate CommitLimit value
Date: Thu, 22 May 2014 13:20:33 -0700 [thread overview]
Message-ID: <537E5C11.1050600@infradead.org> (raw)
In-Reply-To: <1400760284.3145.15.camel@holly>
On 05/22/2014 05:04 AM, Petr Oros wrote:
> The formula to calculate "CommitLimit" value mentioned in kernel documentation is incorrect.
> Right formula is: CommitLimit = ([total RAM pages] - [total huge TLB pages]) * overcommit_ratio / 100 + [total swap pages]
>
> Signed-off-by: Petr Oros <poros@redhat.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Jiri, please grab this patch.
Thanks.
> ---
> Documentation/filesystems/proc.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
> index 8b9cd8e..b58d764 100644
> --- a/Documentation/filesystems/proc.txt
> +++ b/Documentation/filesystems/proc.txt
> @@ -854,7 +854,8 @@ WritebackTmp: Memory used by FUSE for temporary writeback buffers
> if strict overcommit accounting is enabled (mode 2 in
> 'vm.overcommit_memory').
> The CommitLimit is calculated with the following formula:
> - CommitLimit = ('vm.overcommit_ratio' * Physical RAM) + Swap
> + CommitLimit = ([total RAM pages] - [total huge TLB pages]) *
> + overcommit_ratio / 100 + [total swap pages]
> For example, on a system with 1G of physical RAM and 7G
> of swap with a `vm.overcommit_ratio` of 30 it would
> yield a CommitLimit of 7.3G.
>
--
~Randy
prev parent reply other threads:[~2014-05-22 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 12:04 [PATCH] Documentation: incorrect formula to calculate CommitLimit value Petr Oros
2014-05-22 20:20 ` Randy Dunlap [this message]
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=537E5C11.1050600@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=poros@redhat.com \
--cc=trivial@kernel.org \
/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