All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kylo Ginsberg <kylo.ginsberg@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Mapping full 1 GB of memory on a Freescale Book E part
Date: Thu, 9 Jun 2005 15:09:32 -0700	[thread overview]
Message-ID: <61cc712d0506091509527ee680@mail.gmail.com> (raw)

I'm running 2.6.11 on a Freescale 8555 with 1GB of DDR memory. =20
Looking in arch/ppc/mm/fsl_booke_mmu.c, I see that at most 3 TLB
entries will be used to map memory.  Since the max tlb size on
Freescale Book E is 256 MB, this caps mapped in memory at 768 MB.

I've modified fsl_booke_mmu.c to use a 4th TLB, thus mapping the full
1 GB of memory.  However, I'm new to linux memory management, so I'd
appreciate any comments as to whether there are tradeoffs or dangers
here that I am missing.

Thanks,
Kylo

             reply	other threads:[~2005-06-09 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 22:09 Kylo Ginsberg [this message]
2005-06-09 23:07 ` Mapping full 1 GB of memory on a Freescale Book E part Kumar Gala
2005-06-09 23:25   ` Kylo Ginsberg
2005-06-10  1:08     ` Kumar Gala

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=61cc712d0506091509527ee680@mail.gmail.com \
    --to=kylo.ginsberg@gmail.com \
    --cc=linuxppc-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.