lkml.org 
[lkml]   [1998]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Small problem with malloc() tested on 2.1.117/115 (and maybe affecting others)
It is disabled! And it'll still overcommit memory???
(/proc/sys/vm/overcommit_memory contains 0)

Marc SCHAEFER wrote:

> Division by Zero <paradox@maine.rr.com> wrote:
> > I have found that when I malloc() memory and do not access it/clear it,
> > I can malloc() a very large amount (around 2 gigabytes). I only have
> > around 170 MB in swap and ram. If I immediately memset() after each
>
> Look for memory over-committing in the documentation. You can
> disable this if it is a problem for you, but system-wide only,
> and only in 2.1.x
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:44    [W:0.099 / U:0.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site