From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Swap vs No Swap.
Date: Thu, 22 Nov 2001 17:22:35 +0100 [thread overview]
Message-ID: <20011122172235.4ef9e54a.skraw@ithnet.com> (raw)
In-Reply-To: <F128989C2E99D4119C110002A507409801C52F89@topper.hrow.ndsuk.com>
In-Reply-To: <F128989C2E99D4119C110002A507409801C52F89@topper.hrow.ndsuk.com>
On Thu, 22 Nov 2001 16:11:29 -0000
"Elgar, Jeremy" <JElgar@ndsuk.com> wrote:
> Hum think I'm going to test this idea out tonight, quick question without
> swap at what point would the kernel stop giving memory up for cache
> purposes. For example I noticed on Tuesday whist doing a back up of a file
> system (in-line tar cd untar) I was left with ~4 Mb left having nearly the
> rest of my 2Gb Ram used for cache.
>
> Would this ram be given back to the free pool much more readily?
Not to my knowledge. Since I was pretty much bitten by swap in former days I
plugged in more RAM and stopped swap completely. I must admit that it didn't
get any faster, but trashing is gone (obviously). But this is only because of
my own dumbness placing swap on the same drive as root-fs. I guess it would be
a good idea to use the former small hds (1-2 GB) for swap completely, so any
bad interaction with normal fs is omitted.
BTW maybe you should try the latest preX versions, they tend to have more
_free_ mem available and perform pretty ok on my system.
Regards,
Stephan
next prev parent reply other threads:[~2001-11-22 16:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 16:11 Swap vs No Swap Elgar, Jeremy
2001-11-22 16:22 ` Ryan Cumming
2001-11-22 16:22 ` Stephan von Krawczynski [this message]
[not found] <Pine.LNX.4.10.10111221006010.29736-100000@coffee.psychology.mcmaster.ca>
2001-11-22 16:34 ` war
2001-11-26 20:18 ` Kent Borg
-- strict thread matches above, loose matches on Subject: below --
2001-11-22 16:29 Elgar, Jeremy
2001-11-22 1:53 war
2001-11-22 2:23 ` Joel Jaeggli
2001-11-22 2:31 ` war
2001-11-22 2:58 ` Mark Hahn
2001-11-22 4:09 ` listmail
2001-11-22 5:24 ` H. Peter Anvin
2001-11-22 5:30 ` war
2001-11-22 5:32 ` H. Peter Anvin
2001-11-22 9:50 ` Christian Bornträger
2001-11-22 8:50 ` Rik van Riel
2001-11-22 11:00 ` James A Sutherland
2001-11-22 16:00 ` war
2001-11-22 16:08 ` James A Sutherland
2001-11-22 16:57 ` Rik van Riel
2001-11-22 18:56 ` François Cami
2001-11-22 18:58 ` James A Sutherland
2001-11-22 19:17 ` François Cami
2001-11-22 19:36 ` G . Sumner Hayes
2001-11-22 20:37 ` James A Sutherland
2001-11-23 6:30 ` Charles Marslett
2001-11-23 9:13 ` James A Sutherland
2001-11-23 16:46 ` Charles Marslett
2001-11-22 16:25 ` war
2001-11-22 16:37 ` Ryan Cumming
2001-11-22 17:39 ` James A Sutherland
2001-11-22 17:56 ` war
[not found] ` <01112211150302.00690@argo>
2001-11-22 16:01 ` war
2001-11-22 16:12 ` James A Sutherland
2001-11-22 16:36 ` war
2001-11-22 16:33 ` Bjorn Wesen
2001-11-22 17:37 ` Thomas S. Iversen
2001-11-22 21:18 ` Mike Galbraith
2001-11-22 17:41 ` James A Sutherland
2001-11-22 17:56 ` war
2001-11-22 18:08 ` James A Sutherland
2001-11-23 22:05 ` Daniel Gryniewicz
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=20011122172235.4ef9e54a.skraw@ithnet.com \
--to=skraw@ithnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox