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

RE: [Xen-ia64-devel] kernel build performance data with dom0_VP modeopen


  • To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 25 May 2006 10:28:30 -0700
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 25 May 2006 10:28:41 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZ/nb1f0XHdQJjcRWe/RBQSHeRtBQAgjXcQ
  • Thread-topic: [Xen-ia64-devel] kernel build performance data with dom0_VP modeopen

> For dom0vp model, VHPT size is reduced to 64KBytes to avoid
> triggering software lock detection.
> For P=M model, its size remain 64MB.
> It would be interesting to measure on P=M model with 64KBtyes 
> VHPT size.
> (Edit VHPT_SIZE_LOG2 in xen/include/asm-ia64/vhpt.h)

Yes, having a VHPT that is 1024x smaller is likely
to make a big difference in performance.  I'm surprised
it isn't worse!

I agree it would be interesting to measure P==M with
the smaller vhpt (Jingke, is this a measurement you
could easily make on your system?), but since we are
definitely moving ahead with VP it would be good to
look forward rather than back.

Can you explain in more detail about the software lock
detection and why a 64KB VHPT avoids it?  Any ideas on
how to get to a larger VHPT (not necessarily as large
as 64MB)?

Thanks,
Dan

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