From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Translation cache sizes
Date: Sat, 8 Apr 2006 04:13:52 +0100 [thread overview]
Message-ID: <200604080413.52908.jseward@acm.org> (raw)
Using qemu from cvs simulating x86-softmmu (no kqemu) on x86,
booting SuSE 9.1 and getting to the xdm (kdm?) graphical login
screen, requires making about 1088000 translations, and the
translation cache is flushed 17 times. Booting is not too bad,
but once user-mode starts to run the translation cache is pretty
much hammered.
I made 2 changes:
* increase CODE_GEN_BUFFER_SIZE from 16*1024*1024
to 64*1024*1024,
* observe that CODE_GEN_AVG_BLOCK_SIZE of 128
for the softmmu case is too low; my measurements put it
at about 247. So I changed it to 256.
With those changes in place, the same boot-to-kdm process
requires only about 570000 translations to be made, and 2
cache flushes to happen. Of course the cost is an extra
48M of memory use.
J
next reply other threads:[~2006-04-08 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 3:13 Julian Seward [this message]
2006-04-08 6:30 ` [Qemu-devel] Translation cache sizes Mulyadi Santosa
2006-04-08 10:27 ` Johannes Schindelin
2006-04-08 12:43 ` Gwenole Beauchesne
2006-04-08 13:10 ` Paul Brook
2006-04-08 13:16 ` Paul Brook
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=200604080413.52908.jseward@acm.org \
--to=jseward@acm.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).