Messages in this thread | | | Date | Sun, 23 Aug 1998 11:32:51 +0200 (CEST) | From | Rik van Riel <> | Subject | Re: Small problem with malloc() tested on 2.1.117/115 (and maybe affecting others) |
| |
On 23 Aug 1998, 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
Note that this doesn't fully turn of memory overcommits, it is just a partial 'solution' to the (IMHO) non-problem. It works in most cases, however.
Rik. +-------------------------------------------------------------------+ | Linux memory management tour guide. H.H.vanRiel@phys.uu.nl | | Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ | +-------------------------------------------------------------------+
- 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
| |