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

RE: [Xen-ia64-devel] [PATCH] [RESEND] domU destroy & page ref counter


  • To: "Masaki Kanno" <kanno.masaki@xxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Mon, 13 Mar 2006 10:51:41 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 13 Mar 2006 02:52:46 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZEzk73b8m9crTqRDGnrH2eXx6IAQBc90qQ
  • Thread-topic: [Xen-ia64-devel] [PATCH] [RESEND] domU destroy & page ref counter

>From: Masaki Kanno [mailto:kanno.masaki@xxxxxxxxxxxxxx]
>Sent: 2006年3月11日 13:37
>As for this patch, page faults occurs in living domains to flush all VHPT
>and all TBL. That is I think that performance of living domains becomes bad
>temporarily. However, I thought that a serious problem did not occur so that
>entries was inserted in VHPT and TLB again.
>Because xen/ia64 was not able to destroy a domain for a long time, I made
>this patch to be able to destroy a domain as possible simply.
>I think that I have to remake an allocation logic of RID to take the benefit
>of RID partition. I think that this remaking is assignment given me.
>
Kanno,
It's great for you to do this!
More thinking about this,
Currently, the rid range allocated for a domain has fixed relationship to
this domain's ID. I am not sure the domain ID allocation mechanism. For example,
when you destroy dom3 and create a new one, the new domain's ID is 3 or 4? I'm 
not sure. If the new domain' ID is 3, Maybe we need to breakdown the 
relationship
between domain ID and the allocated rid ragne to reduce the VHPT and machine TC
flush.

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