From: "Corey McGuire" <coreyfro@coreyfro.com>
To: linux-raid@vger.kernel.org
Subject: Re: Mirroring swap
Date: Thu, 26 Jun 2003 19:14:50 -0700 [thread overview]
Message-ID: <200306261914500491.05546D13@ilneval.coreyfro.com> (raw)
In-Reply-To: <20030626215606.A29149@newbox.localdomain>
I'd like to know if Linux can address more than 4GB's of RAM (on a 32 bit processor without using dirty tricks like Intel's 36bit hack) including the swap system.
I am pretty sure that all OS's using 32bit CPU's in a 32bit way can only address 4GB's of RAM, including swap. Ergo, when RAM gets cheap enough, swap could become obsolete.
I'll probably have to blow out my raid before all is done with me. Anyone know a way I could occupie 4GB's or more RAM quickly?
*********** REPLY SEPARATOR ***********
On 6/26/2003 at 9:56 PM Scott McDermott wrote:
>Corey McGuire on Thu 26/06 14:44 -0700:
>> In Linux, is there a reason for using swap if you can
>> afford the RAM?
>
>Hmm...if you really aren't using some pages, why not have
>them paged out during some idle time and have more free
>physical memory available immediately without having to wait
>for pageout, should demand occur? I don't know if Linux will
>ever page out even very old pages if there is no memory
>pressure at all, but it probably makes sense to do so in
>order to have memory available immediately, should a huge
>demand occur. Then again, should those pages be demanded
>again, you would have to wait for pagein. I wonder what
>Linux does?
>-
>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/psearch.php3?st=coreyfro
ICQ : 3168059
-----BEGIN GEEK CODE BLOCK-----
GCS !d--(+) s: a- C++++$ UL++>++++ 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//
next prev parent reply other threads:[~2003-06-27 2:14 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
2003-06-27 1:56 ` Scott McDermott
2003-06-27 2:14 ` Corey McGuire [this message]
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=200306261914500491.05546D13@ilneval.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.