From: Dominic Sweetman <dom@mips.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Johannes Stezenbach <js@convergence.de>,
Dominic Sweetman <dom@mips.com>,
Emmanuel Michon <em@realmagic.fr>,
linux-mips@linux-mips.org
Subject: Re: TLB dimensioning
Date: Thu, 2 Sep 2004 12:53:45 +0100 [thread overview]
Message-ID: <16695.2505.44705.24637@mips.com> (raw)
In-Reply-To: <20040902103137.GB19884@linux-mips.org>
Johannes asked
> > "...the 4Kc core contains a 3-entry instruction TLB (ITLB), a 3-entry
> > data TLB(DTLB), and a 16 dual-entry joint TLB (JTLB) with variable page
> > sizes."
> >
> > What exactly does that mean, and how does it rate performancewise?
> > I'm just curious ;-)
I'd like to believe that if the manual mentions the ITLB and DTLB it
also says, somewhere, what they do...
But as Ralf says they're tiny caches of translation entries,
automatically refilled from the main TLB when required. They work
faster than the main TLB (being smaller) and prevent translations for
loads/stores getting in the way of translations for instruction
fetches. Usually there's a mysterious 1-clock extra delay when the
translation you need isn't in the ITLB/DTLB, but it's only one clock
and doesn't happen very often, so the performance effect is usually
somewhere between unmeasurable and tiny.
> Probably most MIPS implementations since at least the R4600 had ITLB
> and DTLB.
Even the very first MIPS architecture chip (R2000) had an I-side
"uTLB". It had just one entry, but then instructions tend to be
sequential...
--
Dominic Sweetman
MIPS Technologies
prev parent reply other threads:[~2004-09-02 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 10:07 TLB dimensioning Emmanuel Michon
2004-09-01 13:28 ` Dominic Sweetman
2004-09-01 23:35 ` Ralf Baechle
2004-09-02 12:25 ` Dominic Sweetman
2004-09-02 10:19 ` Johannes Stezenbach
2004-09-02 10:31 ` Ralf Baechle
2004-09-02 11:53 ` Dominic Sweetman [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=16695.2505.44705.24637@mips.com \
--to=dom@mips.com \
--cc=em@realmagic.fr \
--cc=js@convergence.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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