From: Stefan Smietanowski <stesmi@stesmi.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Rudolf Usselmann <rudi@asics.ws>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
"Frank Denis (Jedi/Sector One)" <j@pureftpd.org>,
linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: kernel (64bit) 4GB memory support
Date: Thu, 12 May 2005 05:56:17 +0200 [thread overview]
Message-ID: <4282D3E1.80303@stesmi.com> (raw)
In-Reply-To: <20050511142745.GQ2281@csclub.uwaterloo.ca>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Lennart Sorensen wrote:
> On Wed, May 11, 2005 at 02:48:42AM +0700, Rudolf Usselmann wrote:
>
>>I do see the full 4G. With Fedora Core 2 32bit, I can use all
>>4G as well. All my problems started when I "upgraded" to x86_64 ...
>
>
> In 32bit it probably uses the PSE36 extensions or something, which isn't
> the same thing as flat 64bit memory access. It could just be a matter
> of needing a memory hole somewhere for PCI space or something. I only
> have 1G in my 64bit machine so I haven't got near these problems.
I don't recall him saying he's changed kernel from the default redhat
kernel in which case he's running the RedHat 4G/4G split kernel and not
using PSE/PAE.
// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFCgtPhBrn2kJu9P78RAvRnAKCnSbeH+4i/vzAfRYfWJXgFad3fpACfVQdp
JWUmCke6CvQ1mq5Gj4SvkZM=
=50yt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-05-12 3:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 8:16 kernel (64bit) 4GB memory support Rudolf Usselmann
2004-12-11 10:06 ` Jeff Garzik
2004-12-11 10:13 ` Rudolf Usselmann
2004-12-11 11:22 ` Andrew Walrond
2004-12-11 17:47 ` Jeff Garzik
2004-12-12 4:12 ` Rudolf Usselmann
2004-12-12 4:41 ` Zwane Mwaikambo
2004-12-12 5:10 ` Rudolf Usselmann
2004-12-12 8:32 ` Zwane Mwaikambo
2004-12-12 9:15 ` Rudolf Usselmann
2004-12-12 16:35 ` Zwane Mwaikambo
2004-12-14 12:25 ` Rudolf Usselmann
2004-12-15 4:22 ` Zwane Mwaikambo
[not found] ` <20041216074905.GA2417@c9x.org>
2004-12-16 16:09 ` Rudolf Usselmann
2004-12-20 19:49 ` Zwane Mwaikambo
2004-12-21 16:23 ` Rudolf Usselmann
2004-12-21 16:33 ` Zwane Mwaikambo
2004-12-21 16:39 ` Rudolf Usselmann
2004-12-21 16:56 ` Zwane Mwaikambo
2005-05-09 15:56 ` Rudolf Usselmann
2005-05-09 20:07 ` Lennart Sorensen
2005-05-10 19:48 ` Rudolf Usselmann
2005-05-10 20:03 ` Lee Revell
2005-05-11 5:02 ` Rudolf Usselmann
2005-05-10 22:58 ` Terry Vernon
2005-05-12 3:53 ` Stefan Smietanowski
2005-05-11 14:27 ` Lennart Sorensen
2005-05-12 3:56 ` Stefan Smietanowski [this message]
2005-05-12 4:04 ` Rudolf Usselmann
2005-05-12 15:13 ` William Lee Irwin III
2005-05-09 20:07 ` Andi Kleen
2005-05-09 22:24 ` Zwane Mwaikambo
2005-05-10 19:50 ` Rudolf Usselmann
2005-05-09 23:13 ` kernel (64bit) 4GB memory support II Andi Kleen
2005-01-13 17:26 ` kernel (64bit) 4GB memory support Rudolf Usselmann
2005-01-14 23:34 ` Zwane Mwaikambo
2005-01-15 5:34 ` Rudolf Usselmann
2005-01-17 4:54 ` Zwane Mwaikambo
2004-12-11 11:35 ` bert hubert
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=4282D3E1.80303@stesmi.com \
--to=stesmi@stesmi.com \
--cc=j@pureftpd.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=rudi@asics.ws \
--cc=zwane@arm.linux.org.uk \
/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