linux-kernel - Re: OOM policy, overcommit control, and soft limits

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080531162341.4e183a09@core>
Date:	Sat, 31 May 2008 16:23:41 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Alan Jenkins <aj504@...york.ac.uk>
Cc:	Chris Frey <cdfrey@...rsquare.net>, linux-kernel@...r.kernel.org
Subject: Re: OOM policy, overcommit control, and soft limits

> In other words, I reckon I have on the order of a gigabyte of virtual
> address space, which has been malloc'ed or equivalent, but is not used
> and therefore requires no memory resource (ram or swap).

No need to reckon. The committed_as in the proc file should give a rough
value.

Alan
--
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/