All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Vincent Lefevre <vincent@vinc17.org>
Cc: linux-kernel@vger.kernel.org,
	"Richard B. Johnson" <root@chaos.analogic.com>
Subject: Re: [2.4.26] overcommit_memory documentation clarification
Date: Sun, 9 May 2004 14:06:11 -0700	[thread overview]
Message-ID: <20040509140611.28e4b2bf.pj@sgi.com> (raw)
In-Reply-To: <20040509022043.GE23263@ay.vinc17.org>

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

  reply	other threads:[~2004-05-09 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-09  0:10 [2.4.26] overcommit_memory documentation clarification Vincent Lefevre
2004-05-09  2:04 ` Richard B. Johnson
2004-05-09  2:20   ` Vincent Lefevre
2004-05-09 21:06     ` Paul Jackson [this message]
2004-05-09 21:49       ` Vincent Lefevre
2004-05-27 12:20         ` Marcelo Tosatti
2004-05-27 12:30           ` Marc-Christian Petersen
2004-05-27 13:09             ` Marcelo Tosatti
2004-05-27 13:19               ` Dave Jones
2004-05-27 21:12               ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040509140611.28e4b2bf.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=vincent@vinc17.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.