From: Kumar Gala <galak@kernel.crashing.org>
To: Aaron Pace <kodiakuppercut@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: e500 lowmem & TLBs
Date: Wed, 21 Oct 2009 15:27:13 -0500 [thread overview]
Message-ID: <2099631E-2454-4816-838D-D82145A3B05B@kernel.crashing.org> (raw)
In-Reply-To: <bc81dc640910210852l7c6d3f11ia0fb5524f952fe9d@mail.gmail.com>
On Oct 21, 2009, at 10:52 AM, Aaron Pace wrote:
> Hello,
>
> For the e500 processors, it appears that the first 3 of 16 permanent
> TLB entries are used to map lowmem. Are the other 13 ever used?
>
not right now. We intend to use them for hugetlbfs support.
- k
prev parent reply other threads:[~2009-10-21 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 15:52 e500 lowmem & TLBs Aaron Pace
2009-10-21 20:27 ` Kumar Gala [this message]
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=2099631E-2454-4816-838D-D82145A3B05B@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=kodiakuppercut@gmail.com \
--cc=linuxppc-dev@ozlabs.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