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

RE: [Xen-ia64-devel] Question about migration


  • To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Fri, 1 Feb 2008 16:01:04 +0800
  • Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 01 Feb 2008 00:01:41 -0800
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AchkqENg5aZRpcL2SXicNDm793gNMwAACHdg
  • Thread-topic: [Xen-ia64-devel] Question about migration

Isaku Yamahata wrote:
> On Fri, Feb 01, 2008 at 03:08:24PM +0800, Xu, Anthony wrote:
>> In DomU, ar.itc is not virtualized, so application can get itc
>> directly. When DomU is migrated, how do you prevent vitc jump a lot(
>> foreward/backward)?
> 
> Currently nothing prevents it. So a big itc jump can happen.
> Anyway user application can be stopped/continued by SIGSTOP/SIGCONT
> so that user application should be tolerable with such a big jump of
> itc. 
Foreward jump may be OK,
How about back-ward jump? Application may be confused.

> 
> So in theory it's ok. But I'm not sure in practical.
> Do you have any concrete examples/scenario in your mind?
No, But I know some DB use ITC,

Anthony

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


 


Rackspace

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