From: Willy Tarreau <w@1wt.eu>
To: "Mouawad, Tony" <Tony.Mouawad@christiedigital.com>
Cc: Pedro <linux_user@izecksohn.com>, linux-kernel@vger.kernel.org
Subject: Re: tmpfs and the OOM killer
Date: Thu, 12 Apr 2007 23:09:44 +0200 [thread overview]
Message-ID: <20070412210944.GK943@1wt.eu> (raw)
In-Reply-To: <AD98412A5373CC4AA643D9C021922A541C4DE0@cdskitexg01.cds.int>
On Thu, Apr 12, 2007 at 04:56:24PM -0400, Mouawad, Tony wrote:
> I have noticed that with overcommit_memory=2 and overcommit_ratio=100,
> my system cannot leverage as much ram as it could if it was configured
> for overcommit_memory=0.
>
> Is this because when overcommit_memory=2, anything that mallocs memory
> but doesn't touch that memory is counted as used memory?
Most probably, yes. This proves that your system may endup doing OOM
in mode 0 if one of your applications suddenly decided to use all the
memory it has allocated.
> I see a value
> in /proc/meminfo called Commited_AS: and it seems to reflect what has
> been malloced in the system but not necessarily touched. Is this true?
Yes (at least I do think so).
Regards,
Willy
next prev parent reply other threads:[~2007-04-12 21:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 5:23 tmpfs and the OOM killer Pedro
2007-04-11 19:48 ` Willy Tarreau
2007-04-11 21:05 ` Mouawad, Tony
2007-04-11 22:27 ` Pedro
2007-04-11 22:39 ` Alan Cox
2007-04-12 5:19 ` Pedro
2007-04-12 9:42 ` Alan Cox
2007-04-12 15:08 ` Pedro
2007-04-12 11:25 ` Theodore Tso
2007-04-12 14:35 ` Pedro
2007-04-12 20:31 ` Willy Tarreau
2007-04-12 20:56 ` Mouawad, Tony
2007-04-12 21:09 ` Willy Tarreau [this message]
2007-04-12 8:13 ` Jan Engelhardt
2007-04-12 8:19 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2007-04-12 5:04 Al Boldi
2007-04-12 5:39 ` Pedro
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=20070412210944.GK943@1wt.eu \
--to=w@1wt.eu \
--cc=Tony.Mouawad@christiedigital.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_user@izecksohn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.