From: David Ashley <dash@xdr.com>
To: linux-kernel@vger.kernel.org
Subject: Cached memory never gets released
Date: Wed, 23 Jun 2004 08:31:12 -0700 [thread overview]
Message-ID: <200406231531.i5NFVCuf018957@xdr.com> (raw)
Linux 2.4.23 on x86, 128M memory available
Free outputs this:
total used free shared buffers cached
Mem: 119204 109592 9612 0 60 92136
-/+ buffers/cache: 17396 101808
Swap: 0 0 0
The root filesystem is NFS, no hard drives involved.
When I run a simple program that just mallocs memory and fills it with
random data, the kernel kills the process after it has only allocated 8 or
9 megs. The 92136K of cached memory can't get released for some reason.
What is happening?
Thanks very much!
-Dave
next reply other threads:[~2004-06-23 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 15:31 David Ashley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 18:35 Cached memory never gets released David Ashley
2004-06-23 18:44 ` Doug McNaught
2004-06-24 14:48 David Ashley
2004-06-24 15:49 ` Ross Biro
2004-06-24 17:14 David Ashley
2004-06-27 3:24 David Ashley
2004-06-29 15:07 David Ashley
2004-06-29 16:00 ` Ross Biro
2004-06-29 16:18 David Ashley
2004-06-30 1:25 ` Ross Biro
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=200406231531.i5NFVCuf018957@xdr.com \
--to=dash@xdr.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