public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Lazarenko <vlad@lazarenko.net>
To: thockin@hockin.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: AMD Athlon64 X2 Dual-core and 4GB
Date: Fri, 28 Oct 2005 18:40:36 +0200	[thread overview]
Message-ID: <43625484.30100@lazarenko.net> (raw)
In-Reply-To: <20051028160403.GA26286@hockin.org>

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

>>>Thus, the question - would I be able to use whole 4G RAM with dual-core amd and
>>>kernel with SMP compiled for i686?
> 
> 
> Why would you use a dual core AMD in 32 bit mode?  Just build an x86_64
> kernel.
> 
> If you want to use 4GB in 32 bit mode, you *need* remapping (or you lose
> part of your memory).  Remapping means you have MORE than 4 GB of physical
> address, which means you need PAE to use it at all.

Because I find my distribution's 64-bit release reasonably unstable yet? :)

Or can I somehow build an x86_64 kernel and keep using 32-bit libc?

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3412 bytes --]

  parent reply	other threads:[~2005-10-28 16:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 21:03 AMD Athlon64 X2 Dual-core and 4GB Vladimir Lazarenko
2005-10-27 21:06 ` Joel Jaeggli
2005-10-27 21:06 ` Alejandro Bonilla
2005-10-28 15:30 ` Eric W. Biederman
2005-10-28 16:04   ` thockin
2005-10-28 16:13     ` Eric W. Biederman
2005-10-28 17:12       ` thockin
2005-10-28 21:27         ` Vladimir Lazarenko
2005-10-28 16:40     ` Vladimir Lazarenko [this message]
2005-10-28 16:52       ` Eric W. Biederman
2005-10-28 19:30         ` Miquel van Smoorenburg
2005-10-28 16:39   ` Vladimir Lazarenko

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=43625484.30100@lazarenko.net \
    --to=vlad@lazarenko.net \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thockin@hockin.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