From: ebiederman@uswest.net (Eric W. Biederman)
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
Hugh Dickins <hugh@veritas.com>,
Frank Dekervel <Frank.dekervel@student.kuleuven.ac.Be>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
<linux-kernel@vger.kernel.org>
Subject: Re: need help interpreting 'free' output.
Date: 30 Oct 2001 11:05:29 -0700 [thread overview]
Message-ID: <m1heshhul2.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0110300917520.8603-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0110300917520.8603-100000@penguin.transmeta.com>
Linus Torvalds <torvalds@transmeta.com> writes:
> HOWEVER, _then_ I started wondering about whether the thing needs to be
> removed from the swap cache at all, and came to the conclusion that for
> the only case we really care about (and the only case where we _can_
> re-use the swap cache page), we don't actually need to remove it from the
> cache in the first place.
There is a second case, though you may be handling it differently now.
Typically the case is swap < RAM. But basically when we don't have
enough have enough swap pages it pays to drop pages from the swap
cache. So in as many places as we can figuring out how to drop
swap pages when the swap space is practically full is important.
The other alternative implementation is to create a logical backing
store for anonymous pages (so the don't need a presence in the page
table) and then we could just walk that backing store and free up swap
space on demand. Though if you can put anonymous pages in the page
cache now, a variation on that idea may be possible. We don't
want to remove the swap from pages that aren't in ram.
> Does anybody see why we have to remove it from the swap cache at all?
Not just for cow.
Eric
next prev parent reply other threads:[~2001-10-30 18:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 11:32 need help interpreting 'free' output Frank Dekervel
2001-10-30 11:46 ` Mike Fedyk
2001-10-30 14:02 ` Frank Dekervel
2001-10-30 16:07 ` Hugh Dickins
2001-10-30 16:51 ` Andrea Arcangeli
2001-10-30 16:52 ` Linus Torvalds
2001-10-30 17:06 ` Andrea Arcangeli
2001-10-30 17:28 ` Linus Torvalds
2001-10-30 17:39 ` Andrea Arcangeli
2001-10-30 17:53 ` Linus Torvalds
2001-10-30 18:16 ` Andrea Arcangeli
2001-10-30 18:28 ` Linus Torvalds
2001-10-30 18:58 ` Andrea Arcangeli
2001-10-30 19:21 ` Linus Torvalds
2001-10-30 20:05 ` Andrea Arcangeli
2001-10-30 20:25 ` Linus Torvalds
2001-10-30 18:05 ` Eric W. Biederman [this message]
2001-10-30 20:47 ` David S. Miller
2001-10-30 18:11 ` Frank Dekervel
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=m1heshhul2.fsf@frodo.biederman.org \
--to=ebiederman@uswest.net \
--cc=Frank.dekervel@student.kuleuven.ac.Be \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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