All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Corey McGuire" <coreyfro@coreyfro.com>
To: linux-raid@vger.kernel.org
Subject: RE: Mirroring swap
Date: Thu, 26 Jun 2003 14:44:28 -0700	[thread overview]
Message-ID: <200306261444280640.52F72FDF@shargaas.coreyfro.com> (raw)
In-Reply-To: <1056662597.10690.6.camel@gregdell.example.com>

Personally, I think that if a system is so vital that it can't afford a
swap failure, then fill it full of RAM.  One can populate a 32bit system to
the max (4GB's) with quality RAM for less than a grand (less than $500 if
you buy real cheap stuff)

I don't know about Linux, but I know in Windows, swap is only vital because
M$ is too lazy to change their code.  Even in windows XP you need swap.
You can turn off "virtual memmory" but swap is just moved to ram (that's
right, real memory pretending to be fake memory pretending to be real
memory)

In Linux, is there a reason for using swap if you can afford the RAM?

*********** REPLY SEPARATOR  ***********

On 6/26/2003 at 2:23 PM Gregory Leblanc wrote:

>On Thu, 2003-06-26 at 01:30, Gordon Henderson wrote:
>[snip]
>> So now with important machines which had mirrored or RAIDed disk
systems,
>> I always put swap on a mirrored or RAID5d device.
>
>Swap on RAID 5 is going to have pretty poor performance, in general. 
>Swap needs to be both high bandwidth and low latency, both for reading
>and writing.  RAID 5 just isn't that.
>	Greg.
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html




/\/\/\/\/\/\ Nothing is foolproof to a talented fool. /\/\/\/\/\/\

coreyfro@coreyfro.com
http://www.coreyfro.com/
http://stats.distributed.net/rc5-64/psummary.php3?id=196879
ICQ : 3168059

-----BEGIN GEEK CODE BLOCK-----
GCS d--(+) s: a-- C++++$ UBL++>++++ P+ L+ E W+++$ N+ o? K? w++++$>+++++$
O---- !M--- V- PS+++ PE++(--) Y+ PGP- t--- 5(+) !X- R(+) !tv b-(+)
Dl++(++++) D++ G+ e>+++ h++(---) r++>+$ y++*>$ H++++ n---(----) p? !au w+
v- 3+>++ j- G'''' B--- u+++*** f* Quake++++>+++++$
------END GEEK CODE BLOCK------

Home of Geek Code - http://www.geekcode.com/
The Geek Code Decoder Page - http://www.ebb.org/ungeek//


  reply	other threads:[~2003-06-26 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 19:39 Mirroring swap Derek Yeung
2003-06-26  7:07 ` Riley Williams
2003-06-26  7:30   ` Matti Aarnio
2003-06-26  8:30   ` Gordon Henderson
2003-06-26 21:23     ` Gregory Leblanc
2003-06-26 21:44       ` Corey McGuire [this message]
2003-06-27  1:56         ` Scott McDermott
2003-06-27  2:14           ` Corey McGuire
2003-06-27  2:24             ` Scott McDermott
     [not found]               ` <200306261957360966.057B8F63@ilneval.coreyfro.com>
2003-06-27  3:22                 ` Corey McGuire
2003-06-27 16:17                   ` Ricky Beam
2003-06-27 18:04                     ` Show me the cache, was " Corey McGuire
2003-06-27 18:24                       ` Ricky Beam
2003-06-27 23:31                         ` Corey McGuire
2003-06-27  8:49       ` Gordon Henderson
2003-06-26  9:46 ` Scott McDermott
  -- strict thread matches above, loose matches on Subject: below --
2003-06-25 19:58 Bailey, Scott

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=200306261444280640.52F72FDF@shargaas.coreyfro.com \
    --to=coreyfro@coreyfro.com \
    --cc=linux-raid@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.