All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0/4] Out-of-sync L1 shadows.
Date: Fri, 20 Jun 2008 18:31:36 +0100	[thread overview]
Message-ID: <485BE978.5020805@eu.citrix.com> (raw)

Hello,

This set of patches let the guest write directly to L1 pagetables, thus
making them temporarily out of sync (OOS) with their shadows. L2 and
higher level page tables are still always emulated.
This let us avoids most of the pagetable write emulations,
resulting in a generic speedup, especially in Windows guests.

The policy implemented in the fourth patch (that put OOS a pagetable 
whenever the guest tries to write to it), has proven to be a win for 
guest with up to 4 vcpus.


Patches:

  - oos-base.patch: implement the basic mechanisms to unsync and resync
    pages at appropriate times;

  - oos-optimize-1.oos_fixups.patch: OOS writable mappings reverse map
    to avoid shadow brute-force search on resyncs;

  - oos-optimize-2.snapshots.patch: add snapshots of guest pages to
    allow faster revalidation of OOS pages on resync;

  - oos-policy.always.patch: always unsync pages on guest writes;


Benchmarks results:

Results for a Windows Server 2003 DDK Build (build -cPzM 3) with warm
cache (third run) on a Core2 6420 @ 2.13GhZ.

              current   OOS        Diff
32bit 1vcpu  05:27.00  04:38.00   -14.98%
PAE 1vcpu    06:49.00  05:05.00   -25.43%
64bit 1vcpu  06:56.00  05:35.00   -19.47%

32bit 2vcpu  03:31.00  03:06.00   -11.85%
PAE 2vcpu    04:07.00  03:17.00   -20.24%
64bit 2vcpu  04:05.00  03:47.00   -7.35%


Thanks,
Gianluca

                 reply	other threads:[~2008-06-20 17:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=485BE978.5020805@eu.citrix.com \
    --to=gianluca.guida@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.