WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

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

To: "Kouya Shimura" <kouya@xxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] Question about migration
From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Date: Sat, 2 Feb 2008 09:43:27 +0800
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 01 Feb 2008 17:43:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <7k4pctezhp.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <51CFAB8CB6883745AE7B93B3E084EBE201702846@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><20080201075806.GJ26750%yamahata@xxxxxxxxxxxxx><51CFAB8CB6883745AE7B93B3E084EBE201702884@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <7k4pctezhp.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchkvhU4cW0wLPgpRGqNpaQLdH536AAflFJQ
Thread-topic: [Xen-ia64-devel] Question about migration
Kouya Shimura wrote:
> Hi,
> 
> In a SMP machine, complete synchronizing ITCs is impossible.
Agree,

But the difference is limited in a small range,
So, when application is migrated to another CPU, it will see ITC > what
it saw last time.
That means, itc difference have to be less than the itc cycle spent on
process switch.
Otherwise, linux kernel needs to re sync the ITC.

> (i.e. each cpu's ITC has some error)
> So small backward jump might occur in native SMP linux
> except that a process is pinned to a cpu.
> Does its DB perform pinning?
I didn't run any DB, just know it.

Anthony



> 
> Thanks,
> Kouya
> 
> Xu, Anthony writes:
>> 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

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