From: "David S. Miller" <davem@davemloft.net>
To: dan@embeddededge.com
Cc: akpm@osdl.org, marcelo.tosatti@cyclades.com,
linux-kernel@vger.kernel.org
Subject: Re: increased translation cache footprint in v2.6
Date: Mon, 27 Jun 2005 12:50:52 -0700 (PDT) [thread overview]
Message-ID: <20050627.125052.108115648.davem@davemloft.net> (raw)
In-Reply-To: <705a40397bb8383399109debccaebaa3@embeddededge.com>
From: Dan Malek <dan@embeddededge.com>
Date: Mon, 27 Jun 2005 11:57:51 -0400
> Because of the configurability of the address space among text, data,
> IO, and uncached mapping, we simply can't test an address bit and
> build a new TLB entry.
Maybe not by testing a bit, but instead via a range test.
cmp %reg, PAGE_OFFSET_BEGIN
bl not_kernel
cmp %reg, PAGE_OFFSET_END
bge not_kernel
Calculate 8MB PTE here
not_kernel:
That's 4 instructions, completely trivial.
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.
You'll be saving tons of memory accesses, and that alone should
count for some significant performance savings especially on
embedded setups. What's more, you'll get 8MB mappings as well,
decreasing the TLB miss rate.
next prev parent reply other threads:[~2005-06-27 19:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 17:23 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 [this message]
2005-06-27 20:35 ` Dan Malek
2005-06-28 6:18 ` Benjamin Herrenschmidt
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
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=20050627.125052.108115648.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=dan@embeddededge.com \
--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
Powered by JetHome