public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Biro <ross.biro@gmail.com>
To: David Ashley <dash@xdr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cached memory never gets released
Date: Tue, 29 Jun 2004 09:00:36 -0700	[thread overview]
Message-ID: <8783be66040629090027010876@mail.gmail.com> (raw)
In-Reply-To: <200406291507.i5TF7NIJ027740@xdr.com>

First it's absolutely normal for cache to fill up all available
memory.  What's not normal is to not free unused cache when memory is
needed.

My best guess is that this isn't a kernel problem, but a bug in flash
and all that memory really is used.  The next step I would do is go
through all of the processes and see how much memory they are all
using.  For example has flashed been mapping files into memory and not
closing them or freeing the memory?

The first thing I would do is run top on a system that you think is
near dying and sort the processes by memory usage.  If you find a
process using lots of memory, that is your culprit.  In any case,
attach the output of ps auxw from a system that is out of memory.

  reply	other threads:[~2004-06-29 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 15:07 Cached memory never gets released David Ashley
2004-06-29 16:00 ` Ross Biro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-29 16:18 David Ashley
2004-06-30  1:25 ` Ross Biro
2004-06-27  3:24 David Ashley
2004-06-24 17:14 David Ashley
2004-06-24 14:48 David Ashley
2004-06-24 15:49 ` Ross Biro
2004-06-23 18:35 David Ashley
2004-06-23 18:44 ` Doug McNaught
2004-06-23 15:31 David Ashley

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=8783be66040629090027010876@mail.gmail.com \
    --to=ross.biro@gmail.com \
    --cc=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