From: Pranith Kumar <bobby.prani@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
"Richard Henderson" <rth@twiddle.net>,
"Andrzej Zaborowski" <balrogg@gmail.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Alexander Graf" <agraf@suse.de>, "Stefan Weil" <sw@weilnetz.de>,
"open list:Overall" <qemu-devel@nongnu.org>,
"open list:AArch64 target" <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [RFC v2 PATCH] tcg/softmmu: Increase size of TLB caches
Date: Thu, 24 Aug 2017 12:02:10 -0400 [thread overview]
Message-ID: <CAJhHMCArPfB_5kraiW=Z047ppFuMsVqxYftNpsZp7Q2KPd49=w@mail.gmail.com> (raw)
In-Reply-To: <20170824155849.30799-1-bobby.prani@gmail.com>
On Thu, Aug 24, 2017 at 11:58 AM, Pranith Kumar <bobby.prani@gmail.com> wrote:
> This patch increases the number of entries cached in the TLB. I went
> over a few architectures to see if increasing it is problematic. Only
> armv6 seems to have a limitation that only 8 bits can be used for
> indexing these entries. For other architectures, the number of TLB
> entries is increased to a 4K-sized cache. The patch also doubles the
> number of victim TLB entries.
>
> A few statistics collected from a build benchmark for various cache
> sizes is below:
>
> | TLB bits\vTLB entires | 8 | 16 | 32 |
> | 8 | 952.94(+0.0%) | 929.99(+2.4%) | 919.02(+3.6%) |
> | 10 | 898.92(+5.6%) | 886.13(+7.0%) | 887.03(+6.9%) |
> | 12 | 878.56(+7.8%) | 873.53(+8.3%)* | 875.34(+8.1%) |
>
> The best combination for this workload came out to be 12 bits for the
> TLB and a 16 entry vTLB cache.
You can find the raw data here: http://paste.ubuntu.com/25383585/
Thanks,
--
Pranith
next prev parent reply other threads:[~2017-08-24 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 15:58 [Qemu-devel] [RFC v2 PATCH] tcg/softmmu: Increase size of TLB caches Pranith Kumar
2017-08-24 16:02 ` Pranith Kumar [this message]
2017-08-28 18:08 ` Richard Henderson
2017-08-28 20:45 ` Richard Henderson
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='CAJhHMCArPfB_5kraiW=Z047ppFuMsVqxYftNpsZp7Q2KPd49=w@mail.gmail.com' \
--to=bobby.prani@gmail.com \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=balrogg@gmail.com \
--cc=crosthwaite.peter@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sw@weilnetz.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;
as well as URLs for NNTP newsgroup(s).