linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: sct@redhat.com
Cc: torvalds@transmeta.com
Subject: 2.3.x swap cache seems to be a big leak
Date: Tue, 25 Apr 2000 05:03:01 -0700	[thread overview]
Message-ID: <200004251203.FAA04709@pizda.ninka.net> (raw)

__delete_from_swap_cache depends upon remove_inode_page doing
a put_page or similar to kill the reference of the swap cache
itself

We changed remove_inode_page during the page cache rewrite such
that is no longer puts the page, the caller does.

If I am right, this causes swap cache pages to never go away.

So if I haven't missed something clever going on here, this would
explain a lot of problems people have reported with swapping making
their machines act weird and eventually run out of ram.

Later,
David S. Miller
davem@redhat.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

             reply	other threads:[~2000-04-25 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-25 12:03 David S. Miller [this message]
2000-06-03 21:32 ` Andrea Arcangeli

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=200004251203.FAA04709@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=sct@redhat.com \
    --cc=torvalds@transmeta.com \
    /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