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

Re: [Xen-devel] [PATCH 0/3] continuable destroy domain: MakeXEN_DOMCTL_destroydomain hypercall continuable


  • To: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>, <yamahata@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Wed, 12 Sep 2007 08:34:55 +0100
  • Delivery-date: Wed, 12 Sep 2007 00:31:04 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acfr2CdZWyirzqyJRAeWmr/EqZ6+lgABbg4wAABwhLAB/LVLkABPPLli
  • Thread-topic: [Xen-devel] [PATCH 0/3] continuable destroy domain: MakeXEN_DOMCTL_destroydomain hypercall continuable

That’s quite surprising. You should add tracing to domain_kill() and find out how many times it gets preempted, how long it runs for between preemptions, etc. and hence find out whether the preemption logic is working at all for you.

 -- Keir


On 11/9/07 22:57, "Krysan, Susan" <KRYSANS@xxxxxxxxxx> wrote:

I tested the patches on Unisys ES7000 x86_64 host using 64-bit SLES10 paravirtualized domains. I compared unstable c/s 15730 and 15826 and unfortunately, the amount of time the host is unresponsive when shutting down large vms has not changed. For example, on a 32x 128gb host, the shutdown of a 62gb vm causes 1 minute and 40 seconds of host unresponsiveness both before and after the patches are applied. Also, I noticed that not only does the amount of unresponsive host time increase when the memory size of the domains increase, but it also increases when the size of the host memory increases.  Here are my test results:

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

 


Rackspace

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