From: Michael Lausch <mla@gams.co.at>
To: ralf@uni-koblenz.de
Cc: linux-kernel@vger.rutgers.edu, linux@cthulhu.engr.sgi.com
Subject: Re: TLB entries > 4kb
Date: Thu, 12 Feb 1998 13:10:02 +0100 [thread overview]
Message-ID: <199802121210.NAA25532@loki.gams.co.at> (raw)
In-Reply-To: Your message of "Thu, 12 Feb 1998 05:56:48 +0100." <19980212055648.54198@uni-koblenz.de>
>>>>> "r" == ralf <ralf@uni-koblenz.de>
>>>>> wrote the following on Thu, 12 Feb 1998 05:56:48 +0100
r> Some architectures can use multiple page sizes in the TLB at the same time.
r> This would for example allow to map memory allocations > PAGE_SIZE using just
r> a single TLB entry if the circumstances are just right, thereby
r> reducing / eleminating TLB trashing. This should improve the performance
r> for huge apps quite a bit. Some architectures could partially get rid of
r> the sick effects of their virtual indexed primary caches as well. All that
r> is needed for this to work is to have sufficiently large physical pages with
r> sufficient alignment at hand.
r> Has anybody ever looked into implementing that? What architectures besides
r> MIPS could take advantage of such a feature?
The MPC860. We now have 8 MByte Page Table entries for the Kernel Address
Space and the Dual Ported RAM used to communicate with the CPM.
r> Ralf
r> -
r> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
r> the body of a message to majordomo@vger.rutgers.edu
next prev parent reply other threads:[~1998-02-12 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-12 4:56 TLB entries > 4kb ralf
1998-02-12 5:50 ` David S. Miller
1998-02-12 8:51 ` Alan Cox
1998-02-12 18:00 ` MOLNAR Ingo
1998-02-12 12:10 ` Michael Lausch [this message]
1998-02-12 22:05 ` J.D. Bakker
-- strict thread matches above, loose matches on Subject: below --
1998-02-12 21:52 David Woodhouse
1998-02-12 21:57 ` Alan Cox
1998-02-12 21:57 ` Alan Cox
1998-02-12 22:00 ` MOLNAR Ingo
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=199802121210.NAA25532@loki.gams.co.at \
--to=mla@gams.co.at \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
/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