public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Al Boldi <a1426z@gawab.com>
Cc: "'Bernd Petrovitsch'" <bernd@firmix.at>,
	"'Linux kernel'" <linux-kernel@vger.kernel.org>,
	"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
	"'Linus Torvalds'" <torvalds@osdl.org>,
	"'Marcelo Tosatti'" <marcelo.tosatti@cyclades.com>,
	"'Vinicius'" <jdob@ig.com.br>
Subject: Re: Kernel doesn't free Cached Memory
Date: Mon, 25 Jul 2005 12:28:58 -0400	[thread overview]
Message-ID: <42E5134A.30001@tmr.com> (raw)
In-Reply-To: <200507230536.IAA03542@raad.intranet>

Al Boldi wrote:
> Dick Johnson wrote: { 
> 
>>On Fri, 2005-07-22 at 08:27 -0300, Vinicius wrote:
>>[...]
>>
>>>   I have a server with 2 Pentium 4 HT processors and 32 GB of RAM, 
>>>this server runs lots of applications that consume lots of memory to. 
>>>When I stop this applications, the kernel doesn't free memory (the  
>>>memory still in use) and the server cache lots of memory (~27GB). 
>>>When I start this applications, the kernel sends  "Out of Memory" 
>>>messages and kill some random applications.
> 
> 
> ...you might even need to turn memory over-commit off:
>   echo "0" > /proc/sys/vm/overcommit_memory
> }
> 
> That's in 2.4. In 2.6 it's:
>   echo "2" > /proc/sys/vm/overcommit_memory

RHEL3 *is* a 2.4 kernel.
> 
> But the kernel doesn't honor no-overcommit in either version, i.e. it still
> overcommits/pages-out loaded/running procs, thus invoking OOM!
> 
> Is there a way to make the kernel strictly honor the no-overcommit request?
> 

Don't have swap?

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-07-25 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22 11:27 Kernel doesn't free Cached Memory Vinicius
2005-07-22 11:41 ` Bernd Petrovitsch
2005-07-22 13:06   ` linux-os (Dick Johnson)
2005-07-23  5:35     ` Al Boldi
2005-07-25 16:28       ` Bill Davidsen [this message]
2005-07-26  5:23         ` Al Boldi
2005-07-22 14:49 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-07-22 16:00 Vinicius
2005-07-22 22:03 ` 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=42E5134A.30001@tmr.com \
    --to=davidsen@tmr.com \
    --cc=a1426z@gawab.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bernd@firmix.at \
    --cc=jdob@ig.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox