From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: "David S. Miller" <davem@davemloft.net>,
akpm@osdl.org, marcelo.tosatti@cyclades.com,
linux-kernel@vger.kernel.org
Subject: Re: increased translation cache footprint in v2.6
Date: Tue, 28 Jun 2005 16:18:22 +1000 [thread overview]
Message-ID: <1119939502.5133.195.camel@gaston> (raw)
In-Reply-To: <dd805c30d3ab223b650077cca3c82d86@embeddededge.com>
On Mon, 2005-06-27 at 16:35 -0400, Dan Malek wrote:
> On Jun 27, 2005, at 3:50 PM, David S. Miller wrote:
>
> > I think you're making this problem more complex than it really
> > is. There is no reason at all to hold page tables for the direct
> > physical memory mappings of lowmem if you have any control whatsoever
> > over the TLB miss handler.
>
> I'm not one to make it more complex, I just want to cover
> all of the possibilities :-) The "compute kernel" part of
> it needs to be generic for all of the possibilities. Like I mentioned.
> we have a quite configurable address space for mapping text,
> data, IO, and uncached spaces. In addition, we have execute
> in place out of flash and other embedded custom options.
> I was hoping to find a solution where the kernel TLBs could
> be dynamically loaded as well, with the standard look up
> algorithm. Yes, I still need a kernel path for the special
> case processing of other than 4K pages, but it would be nice
> to keep that generic as well.
Can't you put the "8Mb page" flag at the PMD level and use normal kernel
page tables ? You'll have to fill PMD entries two by two but that
shouldn't be too difficult.
You can then have the kernel linear mapping use 8Mb pages, along with
some "block IO" translations and leave the rest to normal 4k page tables
Ben.
next prev parent reply other threads:[~2005-06-28 8:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 17:23 increased translation cache footprint in v2.6 Marcelo Tosatti
2005-06-26 23:42 ` Paul Mackerras
2005-06-26 18:31 ` Marcelo Tosatti
2005-06-26 23:49 ` Andrew Morton
2005-06-26 18:52 ` Marcelo Tosatti
2005-06-27 0:33 ` David S. Miller
2005-06-26 19:09 ` Marcelo Tosatti
2005-06-27 0:53 ` David S. Miller
2005-06-27 15:57 ` Dan Malek
2005-06-27 19:50 ` David S. Miller
2005-06-27 20:35 ` Dan Malek
2005-06-28 6:18 ` Benjamin Herrenschmidt [this message]
2005-06-28 13:42 ` Dan Malek
2005-06-27 15:46 ` Dan Malek
2005-06-28 6:21 ` Benjamin Herrenschmidt
2005-06-28 13:49 ` Dan Malek
2005-06-27 1:55 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 19:04 Al Boldi
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=1119939502.5133.195.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=dan@embeddededge.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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