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

Re: [Xen-devel] page ref/type count overflows


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 27 Jan 2009 11:22:19 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 27 Jan 2009 03:22:49 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcmAaWa3nRf+0VeMkUegRKCBGfUbuQACB07k
  • Thread-topic: [Xen-devel] page ref/type count overflows

On 27/01/2009 10:24, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:

> On 27/01/2009 10:16, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
> 
>> Yes, I too realized that on my way home yesterday. The only thing I see as
>> viable for consideration would be to remove the embedded spinlock again, and
>> use the same bit-lock as x86-32 does.
> 
> Makes page_unlock() more expensive on x64. Don't know how much that matters.

I think we could perhaps merge it into type_info and take/release it at the
same time as get_page_type/put_page_type, to avoid extra atomic ops. I'll
look into that.

For the cpumask, I have some ideas there too...

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