mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: AMD64: 64 bit kernel 32 bit userland - some pending questions
Date: Tue, 6 Jun 2006 11:34:56 +0200	[thread overview]
Message-ID: <20060606093456.GL4552@cip.informatik.uni-erlangen.de> (raw)

Hello everyone,
I would like to use an AMD64 Opteron System with a 64 bit Linux Kernel,
but a 32 bit userland (Debian Sarge). I have a few questions about this:

        - Is it possible to give the userland 3Gbyte virtual address
          space (default for 2.4 and 2.6). But give the Kernel a 64 bit
          virtual address space so that I get more than 1 Gbyte physical
          Memory into LOWMEM - say I want 8 Gbyte - without using HIGHMEM
          at all? If this scenario is possible I would get cheap memory
          access at the benefit of a well tested userland. I don't have
          applications that need more than 2 Gbyte virtual address
          space.

        - What is the easiest way to build a 64 bit kernel on a 32 bit
          Debian sarge. Are there crosscompiler packages available? Are
          there any guides on this?

        - If the above scenario works out like I imagine it, does this
          add some additional overhead I am not aware of when I switch
          for example from 32 bit userland to 64 bit kernel space which
          would override the performance gain I get from the huge LOWMEM
          virtuall address space?

        Thomas

             reply	other threads:[~2006-06-06  9:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  9:34 Thomas Glanzmann [this message]
2006-06-06 10:42 ` Andi Kleen
2006-06-06 10:49   ` Thomas Glanzmann
2006-06-06 11:51   ` Rafael J. Wysocki
2006-06-06 11:55     ` Andi Kleen
2006-06-06 11:56       ` Marcus Meissner
2006-06-06 12:11         ` Rafael J. Wysocki
2006-06-07  3:11 Albert Cahalan
2006-06-07  4:08 ` H. Peter Anvin

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=20060606093456.GL4552@cip.informatik.uni-erlangen.de \
    --to=sithglan@stud.uni-erlangen.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

all inboxes | Powered by JetHome®