Messages in this thread | | | Date | Sun, 9 May 2004 14:06:11 -0700 | From | Paul Jackson <> | Subject | Re: [2.4.26] overcommit_memory documentation clarification |
| |
Vincent wrote: > NULL == (void *) 0 and NULL == 0 must be true Yes - NULL is compares equal to both (void *)0 and 0. No - not necessarily the _same_ value - one could be on a system with 32 bit ints, 64 bit pointers, for example.
> The goal of malloc is to reserve memory. It's up to the kernel whether sbrk (used by malloc to obtain virtual address space) reserves memory or not.
Check out: /proc/sys/vm/overcommit_memory Documentation/sysctl/vm.txt - overcommit_memory
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.650.933.1373 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |