From: "John Pearson" <john@illhostit.com>
To: "Erik Mouw" <erik@harddisk-recovery.com>, "Ashley" <ashleyz@alchip.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Kernel cached memory
Date: Fri, 22 Jul 2005 14:43:43 -0700 [thread overview]
Message-ID: <JCEEICIEKCENOEGFMGBACEAGCAAA.john@illhostit.com> (raw)
In-Reply-To: <20050722125746.GG20258@harddisk-recovery.com>
Wouldn't having (practically) all your memory used for cache slow down
starting a new program? First it would have to free up that space, and then
put stuff in that space, taking potentially twice as long. I think there
should be a system call for freeing cached memory, for those that do want to
do it.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Erik Mouw
Sent: Friday, July 22, 2005 5:58 AM
To: Ashley
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel cached memory
On Fri, Jul 22, 2005 at 05:46:58PM +0800, Ashley wrote:
> I've a server with 2 Operton 64bit CPU and 12G memory, and this server
> is used to run applications which will comsume huge memory,
> the problem is: when this aplications exits, the free memory of the
server
> is still very low(accroding to the output of "top"), and
> from the output of command "free", I can see that many GB memory was
cached
> by kernel. Does anyone know how to free the kernel cached
> memory? thanks in advance.
Free memory is bad, it means the memory doesn't have a proper use.
Cached memory will be freed automatically when the kernel needs memory
for other (more important) things.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
-
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/
next prev parent reply other threads:[~2005-07-22 21:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 9:46 Ashley
2005-07-22 11:31 ` Diego Calleja
2005-07-22 12:57 ` Erik Mouw
2005-07-22 21:43 ` John Pearson [this message]
2005-07-23 12:31 ` Denis Vlasenko
2005-07-22 13:25 ` Gábor Lénárt
2005-07-22 17:58 ` Lee Revell
2005-07-23 10:50 ` Oliver Neukum
2005-07-25 16:47 ` Bill Davidsen
2005-07-25 17:03 ` Diego Calleja
2005-07-25 17:07 ` Paolo Ornati
2005-07-25 18:02 ` Bill Davidsen
2005-08-01 10:38 ` Gábor Lénárt
2005-08-01 21:08 ` Bill Davidsen
2005-07-26 0:35 Chuck Ebbert
[not found] <4t5s8-68A-33@gated-at.bofh.it>
[not found] ` <4tdIU-479-9@gated-at.bofh.it>
2005-07-26 5:03 ` Robert Hancock
2005-07-26 15:00 ` Bill Davidsen
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=JCEEICIEKCENOEGFMGBACEAGCAAA.john@illhostit.com \
--to=john@illhostit.com \
--cc=ashleyz@alchip.com \
--cc=erik@harddisk-recovery.com \
--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
Powered by JetHome