All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carron, Thierry" <thierry.carron@hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] VM strict overcommit on RedHat AS 2.1 kernel 2.4.18-e12 ?
Date: Thu, 23 Jan 2003 13:10:14 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805741@msgid-missing> (raw)

Hello,

A customer requires for his internal application a more strict implementation of the VM :
   -> When malloc returns a non-NULL pointer the memory is really available !

How can I obtain this behavior using RedHat  AS 2.1 kernel 2.4.18-e12 ?

I know that Alan Cox has a patch and that a lot of job is currently done in kernel 2.5 .
This patch is partially integrated in the kernel 2.4.18-e12 delivered with the RedHat Advanced Server 2.1. 
But there is a difference between the documentation  about overcommit_memory  in sysctl/vm.txt and the code really implemented in mm/mmap.c
Is there any reason for that ?

Thanks for your help

Thierry CARRON 
> HP Centre de Compétence France
* +33 (0).450.094.031




                 reply	other threads:[~2003-01-23 13:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-ia64-105590709805741@msgid-missing \
    --to=thierry.carron@hp.com \
    --cc=linux-ia64@vger.kernel.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.