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

Doug McNaught wrote:

>Have you tried a kernel that's less than 8 months old? 2.4.26 is current.

Not so easy, we've got some custom modules and the kernel is modified a
little to suit our needs (not related to buffer caches though).

It seems the problem is *not* brought on by the kernel killing XFree86
like I had posted before. Just normal use of the system seems to cause the
Cached value in /proc/meminfo to go up, and it seems it can't go back down
as needed when memory runs low.

What would be helpful is any advice as to where to look in the kernel source
to try and track this down. I followed the path:
fs/proc/proc_misc.c handles /proc/meminfo, the cached value is based on
  page_cache_size
mm/swap.c is what changes page_cache_size in delta_nr_cache_pages() function
linux/swap.h has macros dec_nr_cache_pages inc_nr_cache_pages which call this
mm/filemap.c is the only place that calls dec_nr_cache_pages in function
  remove_page_from_hash_queue
mm/filemap.c function __remove_inode_page and remove_inode_page call that
mm/filemap.c function invalidate_inode_pages and truncate_complete_page
  call those
mm/filemap.c invalide_this_page2 and truncate_list_pages call
  truncate_complete_page
invalidate_inode_pages is called all over the place...

So we're snowballing but I don't know what mechanism is supposed to actually
free the cached pages when the system is low on memory. Any advice would
be welcome.

Thanks--
Dave

             reply	other threads:[~2004-06-24 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 14:48 David Ashley [this message]
2004-06-24 15:49 ` Cached memory never gets released Ross Biro
  -- 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-29 15:07 David Ashley
2004-06-29 16:00 ` Ross Biro
2004-06-27  3:24 David Ashley
2004-06-24 17:14 David Ashley
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=200406241448.i5OEmK60025648@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.