From: Joe Batt <Joe@soliddesign.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PowerPC64 and more
Date: Thu, 21 Jul 2005 20:05:40 -0500 [thread overview]
Message-ID: <1121994340.30306.54.camel@fred.ofc.soliddesign.net> (raw)
In-Reply-To: <1121985441.9483.97.camel@rapid>
On Fri, 2005-07-22 at 00:37 +0200, J. Mayer wrote:
> We agreed with Fabrice that there should be at least one more
> indirection in page mapping, because it would cost too much memory to
> try to map the whole needed memory space in one table, even if we can
> "forget" some of the middle bits in most cases.
I haven't had time to even look at the qemu code, but in my last
emulator, we found it was fastest to keep a sorted array of chunks of
memory instead of some sort of tree.
To fetch a chunk of memory, you would scan through the device list for a
chunk that covered that range and swap it with the previous chunk in the
list. System RAM bubbled to the top and the control structures of a
particular timer that our real code used bubbled to the top. Most
access is to system RAM, so there is only one indirection most of the
time. We had a 15% speed improvement over using a hash table.
(disclaimer, we were implementing in Java, so array access is a bit slow
due to bounds checking.)
Knuth has a name for the data structure, but I don't remember what it
is.
--
Joe Batt <Joe@soliddesign.net>
prev parent reply other threads:[~2005-07-22 1:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 11:15 [Qemu-devel] PowerPC64 and more J. Mayer
2005-07-21 22:10 ` Filip Navara
2005-07-21 22:37 ` J. Mayer
2005-07-21 22:58 ` Filip Navara
2005-07-22 11:56 ` J. Mayer
2005-07-22 1:05 ` Joe Batt [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=1121994340.30306.54.camel@fred.ofc.soliddesign.net \
--to=joe@soliddesign.net \
--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).