public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: <burlingk@cv63.navy.mil>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Semi OT: 64 bit processors, the Linux Kernel, and x86 Gentoo.
Date: Fri, 25 May 2007 18:53:26 +0900	[thread overview]
Message-ID: <AA0639A1EB70AE409130258CE7BDC31806646B18@messenger.cv63.navy.mil> (raw)



> -----Original Message-----
> From: Boyd Stephen Smith Jr. [mailto:bss03@volumehost.net] 
> Sent: Friday, May 25, 2007 6:28 PM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Semi OT: 64 bit processors, the 
> Linux Kernel, and x86 Gentoo.
> 
> 
> On Friday 25 May 2007 04:09:00 burlingk@cv63.navy.mil wrote:
> > So, unless I need the upper memory support, it may be 
> better for me to 
> > just not click the flag for 64bit memory support, and move on?
> 
> IIRC, that's for PAE, which you definitely shouldn't use 
> unless you have 4G of 
> RAM or greater.
> 
> Ticking that box doesn't make your kernel 64-bit though, anymore than 
> supporting 64-bit file offsets makes a kernel 64-bit.
> 

What makes the difference between a 64 bit kernel, and a 32 bit kernel?
 
--
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2007-05-25  9:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25  9:53 burlingk [this message]
2007-05-25 11:08 ` [gentoo-user] Semi OT: 64 bit processors, the Linux Kernel, and x86 Gentoo Boyd Stephen Smith Jr.
2007-05-25 12:31   ` Denis
2007-05-25 13:06     ` Florian Philipp
  -- strict thread matches above, loose matches on Subject: below --
2007-05-25 14:12 burlingk
2007-05-25 19:54 ` Peter Alfredsen
2007-05-25 12:44 burlingk
2007-05-25 13:54 ` Peter Alfredsen
2007-05-25  9:09 burlingk
2007-05-25  9:28 ` Boyd Stephen Smith Jr.
2007-05-25  7:12 burlingk
2007-05-25  8:07 ` Boyd Stephen Smith Jr.

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=AA0639A1EB70AE409130258CE7BDC31806646B18@messenger.cv63.navy.mil \
    --to=burlingk@cv63.navy.mil \
    --cc=gentoo-user@lists.gentoo.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