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

Re: [Xen-devel] long latency of domain shutdown


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 08 May 2008 11:52:54 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 08 May 2008 03:53:31 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aciw+arc6U5a7RzsEd28OwAX8io7RQ==
  • Thread-topic: [Xen-devel] long latency of domain shutdown

On 8/5/08 11:39, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> No, here I mean having just RELMEM_xen and RELMEM_l{1,2,3,4}.
> Then simply release Xen pages first, then l4...l1.
> 
> For the suggested workaround to reduce latency of relinquish_memory()
> preemption, I simply mean utilizing the code to deal with circular
> references also for releasing simple ones (that code path doesn't seem
> to care to force the type count to zero, but as I understand that's no
> problem since these pages end up being freed anyway, and that's
> where the whole type_info field gets re-initialized - or was this
> happening when the page gets allocated the next time).

You've lost me. Either you are confused or I have forgotten the details of
how that shutdown code works. Either is quite possible I suspect. :-)
Basically I don't see how this avoids the recursive, and potentially rather
expensive, teardown. Nor am I convinced about how much potential time-saving
there is to be had here.

 -- Keir



_______________________________________________
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®.