From: Jakob Oestergaard <jakob@unthought.net>
To: Christoph Pleger <Christoph.Pleger@uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 10 GB in Opteron machine
Date: Fri, 22 Jul 2005 12:39:55 +0200 [thread overview]
Message-ID: <20050722103955.GI30510@unthought.net> (raw)
In-Reply-To: <20050722113138.5d81c770.Christoph.Pleger@uni-dortmund.de>
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
On Fri, Jul 22, 2005 at 11:31:38AM +0200, Christoph Pleger wrote:
> Hello,
...
> > There is no highmem option for the 64-bit kernel, because it doesn't
> > need one.
>
> I have two questions:
>
> 1. Is it possible to compile a 64-bit kernel on a 32-bit machine (or at
> least on a 64-bit machine with 32-bit software) and if yes, how can I do
> that?
Yes. On Debian Sarge, I have a few wrapper scripts to accomplish it -
all attached to this mail - just untar them in /usr/local/bin on a
standard x86 32-bit Sarge distro. Use 'kmake' instead of 'make' when
you are working with your kernel source (eg. 'kmake menuconfig', 'kmake
all')
Sarge comes with all the necessary toolchain support to build a 64-bit
kernel.
It should be equally possible on most other distros of course, I just
haven't felt the urge to go waste my time with them :)
> 2. All other software on the machine is 32-bit software. Will that
> software work with a 64-bit kernel?
Yes. You tell your 64-bit kernel to enable 'IA32 Emulation' (under
Executable file formats / Emulations).
This is really the clever way to run a 64-bit system - 99% of what is
commonly run on most systems only gains overhead from the 64-bit address
space - tools like postfix, cron, syslog, apache, ... will not gain from
being native 64-bit.
The kernel however will gain from being 64-bit - and it will easily run
your existing 32-bit apps.
Solaris has done this for ages - maintaining a mostly 32-bit user space,
a 64-bit kernel, and then allowing for certain memory intensive
applications to run natively 64-bit.
It's a nice way to run a Linux based system too, IMO.
--
/ jakob
[-- Attachment #2: kmake.tar --]
[-- Type: application/x-tar, Size: 10240 bytes --]
next prev parent reply other threads:[~2005-07-22 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 8:55 10 GB in Opteron machine Christoph Pleger
2005-07-22 9:05 ` Jeff Garzik
2005-07-22 9:31 ` Christoph Pleger
2005-07-22 10:17 ` Bernd Petrovitsch
2005-07-22 10:17 ` Bernd Petrovitsch
2005-07-22 10:39 ` Jakob Oestergaard [this message]
2005-07-22 11:37 ` Christoph Pleger
2005-07-22 13:55 ` Jakob Oestergaard
2005-07-25 10:41 ` Christoph Pleger
2005-07-22 12:57 ` Stephen Frost
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=20050722103955.GI30510@unthought.net \
--to=jakob@unthought.net \
--cc=Christoph.Pleger@uni-dortmund.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