From: Scott McDermott <vaxerdec@frontiernet.net>
To: linux-raid@vger.kernel.org
Subject: Re: Mirroring swap
Date: Thu, 26 Jun 2003 22:24:47 -0400 [thread overview]
Message-ID: <20030626222447.C29149@newbox.localdomain> (raw)
In-Reply-To: <200306261914500491.05546D13@ilneval.coreyfro.com>; from coreyfro@coreyfro.com on Thu, Jun 26, 2003 at 07:14:50PM -0700
Corey McGuire on Thu 26/06 19:14 -0700:
> 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.
Without PAE (36-bit), then of course the limit is 32-bit
addressing.
You're right that 4G is not that expensive, but only certain
workloads can actually use this much memory. If your
working set is only 256M, but you often do other work with
different working sets, this is a good candidate for disk
swap. Since you only use the one working set at a time, you
really don't need to fit all of your working sets in core at
once and you are just wasting money. Disk is still MUCH
cheaper than fast memory.
next prev parent reply other threads:[~2003-06-27 2:24 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
2003-06-27 2:24 ` Scott McDermott [this message]
[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=20030626222447.C29149@newbox.localdomain \
--to=vaxerdec@frontiernet.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox