From: "Gong Zhuo" <gongzhuo@163.net>
To: "Linux PPC Mailing List" <linuxppc-embedded@lists.linuxppc.org>
Subject: Any docments analyzing linuxppc kernel and it's policy?
Date: Wed, 13 Sep 2000 20:27:50 +0800 [thread overview]
Message-ID: <012101c01d7e$097f5b00$4607a8c0@LocalHost> (raw)
Hi:
I am reading the source code of linuxppc mm. It seems that the process
uses the logical address 0 - 0x7fffffff, and the kernel uses the logical
address 0xc0000000 -- (0xc0000000 + maxium memory). The rest logical address
will not be used by anyone. Am I right?
Is there any document analyzing the linuxppc kernel and how does the
kernel arrange all the logical space ?
Thanks
Gong Zhuo
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-09-13 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 12:27 Gong Zhuo [this message]
2000-09-14 0:22 ` Any docments analyzing linuxppc kernel and it's policy? Graham Stoney
[not found] <014301c01d7f$a1592540$4607a8c0@LocalHost>
2000-09-13 16:34 ` Dan Malek
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='012101c01d7e$097f5b00$4607a8c0@LocalHost' \
--to=gongzhuo@163.net \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).