From: LA Walsh <law@sgi.com>
To: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Is swap == 2 * RAM a permanent thing?
Date: Thu, 15 Mar 2001 12:11:53 -0800 [thread overview]
Message-ID: <3AB12209.5C2BD495@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0103152344260.1320-100000@duckman.distro.conectiva>
The not reclaiming swap space is flawed in more than once instance.
Suppose my P1 and P2 have their swap reserved -- now both grow.
P3 is idle but can't fit in swap. This is going to result in fragmentation
no? How is this fragmentation less worse than just freeing swap.
Ever since Ram sizes got to about 256M, I've tended toward using swap spaces
about half my RAM size -- thinking of swap as an 'overflow' place that
really shouldn't get used much if at all. As you mention, not reclaiming
swap space, but having 'double-reservations' for previously swapped
programs becomes a problem fast in this situation. Makes the swap
much less flexible.
--
L A Walsh | Trust Technology, Core Linux, SGI
law@sgi.com | Voice: (650) 933-5338
next prev parent reply other threads:[~2001-03-15 20:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 17:19 Is swap == 2 * RAM a permanent thing? Torrey Hoffman
2001-03-15 19:22 ` William T Wilson
2001-03-16 2:44 ` Rik van Riel
2001-03-15 20:11 ` LA Walsh [this message]
2001-03-16 3:56 ` Rik van Riel
2001-03-15 21:45 ` Andrzej Krzysztofowicz
2001-03-16 5:08 ` Rik van Riel
2001-03-19 15:21 ` Guennadi Liakhovetski
2001-03-17 17:59 ` Boris Pisarcik
2001-03-17 17:53 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2001-03-15 12:28 Mike A. Harris
2001-03-15 13:08 ` Rik van Riel
2001-03-15 14:24 ` Mike Harrold
2001-03-16 0:47 ` Rik van Riel
2001-03-15 16:09 ` christophe barbe
2001-03-15 23:26 ` Rik van Riel
2001-03-15 17:20 ` christophe barbe
2001-03-15 17:43 ` James Lewis Nance
2001-03-16 1:25 ` Rik van Riel
2001-03-15 15:23 ` Ketil Froyn
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=3AB12209.5C2BD495@sgi.com \
--to=law@sgi.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.