lkml.org 
[lkml]   [2000]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Overcommitable memory??
Date
On Fri, 17 Mar 2000 12:43:11 +0000 (GMT), you wrote:

>Hi,
>
>On Tue, 14 Mar 2000 14:32:49 -0300 (BRST), Rik van Riel
><riel@conectiva.com.br> said:
>
>>> Without overcommit that just can not happen. There will be
>>> either a free page of memory or a free page of swap into which
>>> you can swap something else out.
>
>> Without overcommit it can still happen, unless you reserve one
>> page of swap space for every page of data that gets mmap()ed...
>
>Even that doesn't cure things. Think about stack growth.

Quite.

Things become a lot clearer if we stop thinking of it as "overcommit",
and regard it as "demand allocated" instead. malloc() just increases
the upper limit on this area; memory is actually allocated when you
USE the address space you allocated earlier via malloc().


James.

-
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.tux.org/lkml/

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