WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] domU memory allocation questions

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] domU memory allocation questions
From: Ryan Harper <ryanh@xxxxxxxxxx>
Date: Fri, 22 Jul 2005 15:57:00 -0500
Delivery-date: Fri, 22 Jul 2005 20:55:38 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
I've been looking at the alloc_heap_pages() and alloc_domheap_pages()
routines with an eye on making things NUMA (allocate local to a node)
aware.  I've got some counters and I'm seeing something around 35 to 
40 calls to alloc_heap_pages() to get xen and dom0 up.  Then when I
launch domU, the number of allocs goes up by 65k.  This is incurred for
every domU launch.  When launching the domain, a dom_mem_op
([1]increase_reservation) is being called which turns into a
alloc_dom_mem() which calls alloc_domheap_pages().  I've yet to find
what is calling all of those increase_reservation memops.  Can anyone
help explain this or point me to the code I should be looking at?

Thanks in advance.

1. Instrumented alloc_dom_mem() output:
(XEN) mem_op: DOM1 start(0) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(880) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(1751) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(26b2) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(3589) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(4514) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(547b) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(6364) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(71df) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(803a) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(8f52) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(9e70) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(add4) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(bd2e) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(cc95) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(db94) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(ea77) nr_extents(65536) order(0)
(XEN) mem_op: DOM1 start(f89f) nr_extents(65536) order(0)

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@xxxxxxxxxx

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

<Prev in Thread] Current Thread [Next in Thread>