From: alex@foogod.com
To: Rik van Riel <riel@conectiva.com.br>
Cc: alex@foogod.com, Alan Olsen <alan@clueserver.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Recommended swap for 2.4.x.
Date: Tue, 30 Jan 2001 11:13:59 -0800 [thread overview]
Message-ID: <20010130111359.C13819@draco.foogod.com> (raw)
In-Reply-To: <20010130101009.B13819@draco.foogod.com> <Pine.LNX.4.21.0101301612360.1321-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0101301612360.1321-100000@duckman.distro.conectiva>
On Tue, Jan 30, 2001 at 04:22:20PM -0200, Rik van Riel wrote:
> At the moment there is no way to reclaim the swap space if
> the page is shared, and for non-shared pages we haven't
> implemented a way to reclaim swap space.
>
> While reclaiming swap space when you run out is pretty
> trivial to do, Linus doesn't seem to like the idea all
> that much and Disk Space Is Cheap(tm) so it's not very
> high on my list of things to do.
In general, I agree that Disk Space Is Cheap(tm) (though, of course, there are
always unusual cases where it may not be), but my primary concern is for
migration of existing configurations. It sounds like what you're saying is
that if I have a machine with 1GB RAM and 1GB swap that I upgrade from 2.2 to
2.4, all of a sudden this machine has effectively half the VM it used to.
That could cause some rather unexpected behavior, so it's good to know ahead
of time..
I guess it's a good thing this question was brought up.
> > Does this mean that having a swap partition less than or equal
> > to RAM is now effectively pointless?
>
> If you're swapping heavily, yes. If most of your programs
> fit in memory and you're hardly using swap, nothing changes.
I think I'm confused.. are you saying that it's useful to have swap which you
can't use? (What I'm hearing is "if you try to use it it won't work, but if
you don't use it it works fine." I get the feeling I'm missing something
subtle.)
-alex
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-30 19:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 21:51 2.4.0-test12: SiS pirq handling Linus Torvalds
2001-01-29 22:06 ` Sven Koch
2001-01-29 22:57 ` Recommended swap for 2.4.x Alan Olsen
2001-01-29 23:04 ` Linus Torvalds
2001-01-29 23:23 ` alex
2001-01-29 23:45 ` Mike Castle
2001-01-29 23:49 ` William T Wilson
2001-01-30 0:24 ` Kevin Krieser
2001-01-30 5:20 ` Jeff Chua
2001-01-30 19:21 ` James H. Cloos Jr.
2001-01-30 1:20 ` idalton
2001-01-30 11:48 ` Rik van Riel
2001-01-30 18:10 ` alex
2001-01-30 18:22 ` Rik van Riel
2001-01-30 18:40 ` Matthew Kirkwood
2001-01-30 18:43 ` Rik van Riel
2001-01-31 19:59 ` Russell King
2001-01-30 19:13 ` alex [this message]
2001-01-30 19:28 ` Rik van Riel
2001-02-02 13:51 ` Pavel Machek
2001-02-02 22:58 ` Alan Olsen
2001-02-02 20:27 ` Jonathan Morton
2001-01-29 23:17 ` 2.4.0-test12: SiS pirq handling Aaron Tiensivu
2001-01-29 23:44 ` Linus Torvalds
2001-01-30 0:34 ` Aaron Tiensivu
2001-01-31 10:19 ` Martin Diehl
2001-01-30 1:38 ` Adam Huffman
2001-01-31 10:21 ` [PATCH] minor ne2k-pci irq fix Martin Diehl
2001-01-31 12:11 ` davej
2001-02-01 0:01 ` Martin Diehl
2001-02-01 15:06 ` Jeff Garzik
2001-02-02 16:49 ` Martin Diehl
2001-02-02 17:05 ` Jeff Garzik
2001-02-03 20:20 ` Linus Torvalds
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=20010130111359.C13819@draco.foogod.com \
--to=alex@foogod.com \
--cc=alan@clueserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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