linux-kernel - Re: tmpfs and the OOM killer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 12 Apr 2007 23:09:44 +0200
From:	Willy Tarreau <w@....eu>
To:	"Mouawad, Tony" <Tony.Mouawad@...istiedigital.com>
Cc:	Pedro <linux_user@...cksohn.com>, linux-kernel@...r.kernel.org
Subject: Re: tmpfs and the OOM killer

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/