Messages in this thread | | | Date | Sun, 19 Mar 2000 01:58:34 -0600 | From | Mike Castle <> | Subject | Re: Overcommitable memory?? |
| |
On Sat, Mar 18, 2000 at 10:32:25PM +0000, Carlos Morgado wrote: > You don't understand [cm]alloc(). You confusing malloc(), which allocates > space in the process (virtual) space, and calloc() which allocates space and > touches it. malloc() is very needed for the same reason sparce files are > needed.
I thought the libc5/glibc implementations of calloc() made use of kernel guarantees that pages would be allocated zeroed out, and so didn't touch them, so in effect calloc() was virtual as well.
mrc -- Mike Castle Life is like a clock: You can work constantly dalgoda@ix.netcom.com and be right all the time, or not work at all www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc We are all of us living in the shadow of Manhattan. -- Watchmen
- 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/
| |