All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ashley <dash@xdr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Cache memory never gets released
Date: Fri, 25 Jun 2004 07:24:09 -0700	[thread overview]
Message-ID: <200406251424.i5PEO9UX000396@xdr.com> (raw)

Marcelo Tosatti wrote:
>Cached memory can be easily reclaimed, take a look at /proc/meminfo "Inactive"
>list.

Here is /proc/meminfo from a box that has all but exhausted its free memory:
        total:    used:    free:  shared: buffers:  cached:
Mem:  122064896 84348928 37715968        0   634880 74829824
Swap:        0        0        0
MemTotal:       119204 kB
MemFree:         36832 kB
MemShared:           0 kB
Buffers:           620 kB
Cached:          73076 kB
SwapCached:          0 kB
Active:          70380 kB
Inactive:         7324 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       119204 kB
LowFree:         36832 kB
SwapTotal:           0 kB
SwapFree:            0 kB

>Add more swap.

Might as well suggest walking on water. The hardware is set in stone, this is
a software issue :^).

Something is preventing the cached memory to get reused, it's like it's gone
for good.

Is there any count of how often a cached block is accessed? If there is such
a count, and the count has an effect on whether to allow the release of the
cached block, that could explain this behaviour. Because it could turn out
that the cached blocks are accessed thousands of times.

Thanks--
Dave

             reply	other threads:[~2004-06-25 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 14:24 David Ashley [this message]
2004-06-25 14:44 ` Cache memory never gets released Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2004-06-25 15:47 David Ashley
2004-06-25  0:31 David Ashley
2004-06-25 12:34 ` Marcelo Tosatti

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=200406251424.i5PEO9UX000396@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.