From: Eric Blake <eblake@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC 5/5] exec: memory radix tree page level compression
Date: Mon, 11 Nov 2013 10:58:19 -0700 [thread overview]
Message-ID: <52811ABB.60100@redhat.com> (raw)
In-Reply-To: <1384187560-20557-6-git-send-email-mst@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On 11/11/2013 09:41 AM, Michael S. Tsirkin wrote:
> At the moment, memory radix tree is already variable width, but it can
> only skip the low bits of address.
>
> This is efficient if we have huge memory regions but inefficient if we
> are only using a tiny portion of the address space.
>
> After we have built up the map, it's a simple matter to detect
> configurations where a single L2 entry is valid.
>
> We can them speed up the lookup by skipping one or more levels.
s/them/then/
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-11-11 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 16:40 [Qemu-devel] [PATCH RFC 0/5] making address spaces 64 bit wide Michael S. Tsirkin
2013-11-11 16:40 ` [Qemu-devel] [PATCH RFC 1/5] split definitions for exec.c and translate-all.c radix trees Michael S. Tsirkin
2013-11-11 16:40 ` [Qemu-devel] [PATCH RFC 2/5] exec: make address spaces 64-bit wide Michael S. Tsirkin
2013-11-11 16:40 ` [Qemu-devel] [PATCH RFC 3/5] exec: relace leaf with skip Michael S. Tsirkin
2013-11-11 16:41 ` [Qemu-devel] [PATCH RFC 4/5] exec: extend skip field to 3 bits Michael S. Tsirkin
2013-11-11 16:41 ` [Qemu-devel] [PATCH RFC 5/5] exec: memory radix tree page level compression Michael S. Tsirkin
2013-11-11 17:58 ` Eric Blake [this message]
2013-11-11 16:59 ` [Qemu-devel] [PATCH RFC 0/5] making address spaces 64 bit wide Paolo Bonzini
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=52811ABB.60100@redhat.com \
--to=eblake@redhat.com \
--cc=mst@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.