From: Vinicius <jdob@ig.com.br>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel doesn't free Cached Memory
Date: Fri, 22 Jul 2005 13:00:51 -0300 [thread overview]
Message-ID: <20050722_160051_071630.jdob@ig.com.br> (raw)
[-- Attachment #1: Mail message body --]
[-- Type: text/plain, Size: 1378 bytes --]
Em (15:49:49), Alan Cox escreveu:
>On Gwe, 2005-07-22 at 08:27 -0300, Vinicius wrote:
>> Hi all!
>>
>> 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)
>
>See any FAQ on the Linux memory management - memory is reclaimed when
>needed not when nobody is using it. That makes things more efficient.
>
>> 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.
>
>Some RHEL3 kernels had a problem with very large memory sizes and 2.4.
>That should not be the case in the current RHEL3 kernels. 2.6 handles
>very large systems a lot lot better, and of course the fact real
>computers now have 64bit processors has also rather improved life.
>
>Alan
>
>----------
Thanks Alan,
I also read on the Linux-Kernel that the problem may be related to an
exhaustion of your kernels address space, I read that the hugemem-kernel
might be the solution to this case since it has 4GB for the kernel memory
plus 4GB for user process.
How can I define if my kernel memory is beeing exhausted? Does this
exhaustion of kernel memory can cause Out Of memory errors ?
next reply other threads:[~2005-07-22 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 16:00 Vinicius [this message]
2005-07-22 22:03 ` Kernel doesn't free Cached Memory Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2005-07-22 11:27 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
2005-07-26 5:23 ` Al Boldi
2005-07-22 14:49 ` 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=20050722_160051_071630.jdob@ig.com.br \
--to=jdob@ig.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox