[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] vram_dirty vs. shadow paging dirty tracking

To: "Anthony Liguori" <aliguori@xxxxxxxxxx>, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Thu, 15 Mar 2007 11:22:53 +0800
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Mar 2007 20:22:10 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcdmUvFXBaOfAcqkTc63Kt/CF/kZdwAXHQ0A
Thread-topic: [Xen-devel] vram_dirty vs. shadow paging dirty tracking

> 
> Compared to what, just updating the full screen 30 times a second?  I
> suspect that's not as bad as it sounds since SDL will be using a
> XShmImage. 
> 
It depends on how you run the benchmark. In case of multiple VMs case
where multiple Qemus (say 8) are running, this kind of comparation eat
unacceptable cpu cycles.
Eddie

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

References:
- Re: [Xen-devel] vram_dirty vs. shadow paging dirty tracking
  - From: Anthony Liguori

Prev by Date: Re: [Xen-devel] Possibilities with Xen3 compared to IBM Power5 DLPAR
Next by Date: [Xen-devel] [PATCH][HVM] remove qemu shadow_vram patch for performance
Previous by thread: Re: [Xen-devel] vram_dirty vs. shadow paging dirty tracking
Next by thread: [Xen-devel] vlapic warning messages
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.