From: Tim Deegan <Tim.Deegan@citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH][RFC]Provide fast write emulation path to release shadow lock
Date: Tue, 22 Jan 2008 09:26:08 +0000 [thread overview]
Message-ID: <20080122092608.GA12891@york.uk.xensource.com> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F024D8E8C@pdsmsx412.ccr.corp.intel.com>
At 10:20 +0800 on 22 Jan (1200997253), Tian, Kevin wrote:
> We also did series of tests on 32/32pae/32e: (host is 32e)
> 32 32pae 32e
> ----Linux----
> kernel build +1% +0.86% +1.9%
> Specjbb +0.9% +1.61% +0.32%
>
> ----XP----
> Sysbench N/A -0.05% -0.32%(*)
>
> * Sysbench score is not very stable on 32e guest, with up
> to 6% variation observed in 5 rounds running. 32pae is
> stable. 32 XP image was unfortunately corrupted at test
> cycle, so not test yet. Don't want to hold here from getting
> early comments. :-)
>
> I thought the performance gain should be straightforward
> with this patch, and thus would like to know comment
> like:
> - Is it a right direction?
Looks good to me!
> - Is there anything wrong or missed in patch?
Nothing fundamental that I can see by reading through it. One thing I'd
change is to avoid introducing "vfn": a virtual address >> PAGE_SIZE is
just a "page number".
> - Any more benchmarks should we test?
Anything and everything. :) Specially multi-vcpu mixed operations
(e.g. kernel compile + ltp + network traffic) while doing live migrate.
Even when they look as clean as this one, changes in the shadow fault
handler tend to chase out implicit/forgotten assumptions.
Cheers,
Tim.
--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 0DZ, UK.]
next prev parent reply other threads:[~2008-01-22 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 2:20 [PATCH][RFC]Provide fast write emulation path to release shadow lock Tian, Kevin
2008-01-22 9:26 ` Tim Deegan [this message]
2008-01-22 10:01 ` Tian, Kevin
2008-01-22 10:06 ` Tim Deegan
2008-01-22 10:08 ` Tian, Kevin
2008-01-25 1:41 ` Re: [PATCH][RFC]Provide fast write emulation path torelease " Xu, Dongxiao
2008-01-25 1:54 ` Tian, Kevin
2008-01-25 10:00 ` Tim Deegan
2008-01-30 1:32 ` Re: [PATCH][RFC]Provide fast write emulation pathtorelease " Xu, Dongxiao
2008-01-30 9:46 ` Tim Deegan
2008-01-30 13:07 ` Re: [PATCH][RFC]Provide fast write emulationpathtorelease " Xu, Dongxiao
2008-02-12 8:25 ` Tim Deegan
2008-02-14 1:54 ` Tian, Kevin
2008-02-15 6:06 ` [PATCH][UPDATE]Provide fast write emulation path Tian, Kevin
2008-02-15 10:01 ` Keir Fraser
2008-02-15 11:36 ` Tim Deegan
2008-02-15 12:21 ` Tian, Kevin
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=20080122092608.GA12891@york.uk.xensource.com \
--to=tim.deegan@citrix.com \
--cc=kevin.tian@intel.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.