From: Stefan Smietanowski <stesmi@stesmi.com>
To: Bernd Eckenfels <ecki@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a 15 GB file on tmpfs
Date: Fri, 22 Jul 2005 13:00:18 +0200 [thread overview]
Message-ID: <42E0D1C2.8080703@stesmi.com> (raw)
In-Reply-To: <E1Dvusr-00048r-00@calista.eckenfels.6bone.ka-ip.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bernd Eckenfels wrote:
> In article <200507201416.36155.naber@inl.nl> you wrote:
>
>>The machine we plan to buy is a HP Proliant Xeon machine and I want to run a
>>32 bit linux kernel on it (the xeon we want doesn't have the 64-bit stuff
>>yet)
>
>
> You cant have 16GB of Memory with 32bit CPUs.
PAE
CONFIG_HIGMEM64G
Supports a 36bit address space, which Xeons do support.
That doesn't mean a program can access it, you still
have the same old limitations per process.
// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFC4NHCBrn2kJu9P78RApKpAKCEUzgKKRY8VG8XIwlCBrTzWpE7LwCdGUss
bSM49ZnzRgFxJ4h0WF5Ulio=
=zwUX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-07-22 10:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 12:16 a 15 GB file on tmpfs Bastiaan Naber
2005-07-20 13:20 ` Erik Mouw
2005-07-20 13:31 ` Antonio Vargas
2005-07-20 13:35 ` Miquel van Smoorenburg
2005-07-20 14:44 ` Erik Mouw
2005-07-20 15:23 ` Antonio Vargas
2005-07-21 2:13 ` Jim Nance
2005-07-20 15:18 ` Jan Engelhardt
2005-07-21 6:25 ` Denis Vlasenko
2005-07-21 8:42 ` Bernd Petrovitsch
2005-07-21 9:12 ` Stefan Smietanowski
2005-07-21 9:39 ` Bernd Petrovitsch
2005-07-22 10:36 ` Bernd Eckenfels
2005-07-22 11:00 ` Stefan Smietanowski [this message]
2005-07-22 16:25 ` Bernd Eckenfels
2005-07-22 21:10 ` Stefan Smietanowski
-- strict thread matches above, loose matches on Subject: below --
2005-07-21 15:25 Andrew Burgess
2005-07-22 9:39 Cabaniols, Sebastien
2005-07-22 10:38 linux
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=42E0D1C2.8080703@stesmi.com \
--to=stesmi@stesmi.com \
--cc=ecki@lina.inka.de \
--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