From: Andi Kleen <andi@firstfloor.org>
To: Yoav Artzi <yoavar@checkpoint.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel memory and split on 64-bit machines
Date: Mon, 29 Oct 2007 13:11:15 +0100 [thread overview]
Message-ID: <p73abq23yu4.fsf@bingen.suse.de> (raw)
In-Reply-To: <4725C1EB.10205@checkpoint.com> (Yoav Artzi's message of "Mon\, 29 Oct 2007 13\:20\:11 +0200")
Yoav Artzi <yoavar@checkpoint.com> writes:
> I am researching now about the Linux kernel memory on 64-bit (x86_64)
> machines. I am looking into answering the following questions:
>
> 1. Is there a user-kernel split on 64-bit memories? If so, how is it
> done? What is the size of each part?
See Documentation/x86_64/mm.txt. Note it changed in 2.6.11.
-Andi
next prev parent reply other threads:[~2007-10-29 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 11:20 Linux kernel memory and split on 64-bit machines Yoav Artzi
2007-10-29 12:11 ` Andi Kleen [this message]
[not found] ` <4725EC21.7000603@checkpoint.com>
[not found] ` <20071029150035.GA30851@one.firstfloor.org>
[not found] ` <4725F6F7.6020702@checkpoint.com>
2007-10-29 15:48 ` Andi Kleen
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=p73abq23yu4.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yoavar@checkpoint.com \
/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