public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: war <war@starband.net>
To: James A Sutherland <jas88@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Swap vs No Swap.
Date: Thu, 22 Nov 2001 12:56:59 -0500	[thread overview]
Message-ID: <3BFD3C6B.B23D0A97@starband.net> (raw)
In-Reply-To: <3BFC5A9B.915B77DF@starband.net> <E166rbB-0005LC-00@mauve.csi.cam.ac.uk> <3BFD2709.31A1A85E@starband.net> <E166xok-0000Nm-00@mauve.csi.cam.ac.uk>

Thank you for understanding!

James A Sutherland wrote:

> On Thursday 22 November 2001 4:25 pm, war wrote:
> > Why have SWAP if you don't need it - answer that.?
>
> Having it is supposed to improve performance. If you take two identical
> machines, and enable swap on one but not the other, the first machine should
> have better performance: it can cache the FS more effectively.
>
> Now, if you have INSANE amounts of RAM (i.e. enough to have everything
> running in RAM *AND* every file you access cached) the swap will make no
> difference at all. Under any other circumstances, it should make things
> better.
>
> James.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2001-11-22 17:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22  1:53 Swap vs No Swap 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 [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
2001-11-22 16:11 Elgar, Jeremy
2001-11-22 16:22 ` Ryan Cumming
2001-11-22 16:22 ` Stephan von Krawczynski
2001-11-22 16:29 Elgar, Jeremy
     [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

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=3BFD3C6B.B23D0A97@starband.net \
    --to=war@starband.net \
    --cc=jas88@cam.ac.uk \
    --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