From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH,RFC]: Generic memory callback regions
Date: Tue, 01 Jun 2004 12:26:43 +0100 [thread overview]
Message-ID: <1086089203.21922.70.camel@sherbert> (raw)
In-Reply-To: <1086088420.21275.6.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Tue, 2004-06-01 at 06:13 -0500, Joe Batt wrote:
> I haven't read your patch, but I recently wrote a SH2 emulator. We
> found that a lot of time was spent finding the right callbacks, so for
> the device memory, we used a sorted array. After each access, we
> bubbled that memory region closed to the beginning of the array. This
> turned out to be faster than the tree that we were using. The main
> differences are we have 100+ regions and implemented it in Java.
Good call. Move-to-front heuristic seems smart because I anticipate (and
you found out for real) that memory accesses will have temporal
locality. Moving to head is theoretically the same or a little better
than 'bubbling up' actually, Knuth covers it in Vol 3 as i recall.
Well, it becomes irrelevent for this case now, as I am implementing this
privately in pciproxy.c, rather than publically in exec.c, and in my
case the list is always 1 item long :)
--
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-06-01 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 2:53 [Qemu-devel] [PATCH,RFC]: Generic memory callback regions Gianni Tedesco
2004-06-01 11:13 ` Joe Batt
2004-06-01 11:26 ` Gianni Tedesco [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=1086089203.21922.70.camel@sherbert \
--to=gianni@scaramanga.co.uk \
--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).