subject:"\[XenPPC\] Re\: xen heap size"

[XenPPC] Re: xen heap size

2007-02-23 Thread Ryan Harper

* Hollis Blanchard [EMAIL PROTECTED] [2007-02-22 16:30]:
 On Thu, 2007-02-22 at 16:07 -0600, Ryan Harper wrote:
 
  IIRC, when dom0 boots with 192MB (the default) I usually see ~19MB of
  heap available in the boot messages on js20.  Looking at js21, I see:
  
  (XEN) Xen Heap: 135MiB (138548KiB)
  
  RMA different size on js21? 
 
 That's an unusual size: it's slightly more than the second 64MB RMA
 boundary, which seems to indicate there's a lot of wasted memory before
 dom0 at 192MB. I wonder if this is related to the 4GB of memory in this
 system. A more complete boot log might shed some light on it.

Attached.

 
 To answer your question, the 970MP (in JS21) supports the same RMA sizes
 as 970 and 970FX (in JS20).

OK.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
[EMAIL PROTECTED]
0  boot net1 xen || root=/dev/sda3
Trying to load: xen || root=/dev/sda3 from: /ht/[EMAIL PROTECTED]/[EMAIL 
PROTECTED],1 ...

 Bootloader 1.5
  Reading MAC address from device: 00:14:5E:9C:1C:C5
  Requesting IP address via BOOTP: 9.3.189.7
  Requesting file leaf4 via TFTP
  Receiving data: ##A##-
  TFTP: Received leaf4 (9428 KBytes)
  Successfully loaded
---
OF: Xen/PPC version 3.0-unstable ([EMAIL PROTECTED]) (gcc version 4.1.0 (SUSE 
Linux)) Mon Feb 19 17:24:41 CST 2007
boot_of_init args: 0x0 0x0 0xe11027c 0xe291b0f 0x15
boot msr: 0x10003000
boot_of_init: _start 0040 _end 00c45c90 0xe291b0f
bootargs = xen || root=/dev/sda3
boot_of_module: Dom0 is linked in: 0x479b4c[size 0x758860]
mod0: 177 E L F
boot_of_module: dom0 mod @ 0x00479b4c[0xbd23ac]
boot_of_module: dom0 mod string: root=/dev/sda3
instantiating RTAS at: 0x4000
creating oftree at: 0xc000
pkg_save: saved device tree in 0x57b8 bytes
boot_of_devtree: devtree mod @ 0xc000 - 0x0003c000
OF: timebase-frequency = 14318378 Hz
OF: clock-frequency = 230 KHz
spinning up secondary processor #1: ping = 0x: pong = 0x1
spinning up secondary processor #2: ping = 0x: pong = 0x2
spinning up secondary processor #3: ping = 0x: pong = 0x3
pruning `/ht/[EMAIL PROTECTED]/[EMAIL PROTECTED]' from devtree
pruning `/ht/[EMAIL PROTECTED]/[EMAIL PROTECTED]' from devtree
boot_of_serial: ISA base: 0xf400
boot_of_serial: ISRC=0x44, but forcing poll mode
 __  ___  ___ __ _
 \ \/ /___ _ __   |___ / / _ \_   _ _ __  ___| |_ __ _| |__ | | ___
  \  // _ \ '_ \|_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |(_)___/\__,_|_| |_|___/\__\__,_|_.__/|_|\___|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0-unstable ([EMAIL PROTECTED]) (gcc version 4.1.0 (SUSE Linux)) 
Mon Feb 19 17:24:41 CST 2007
 Latest ChangeSet: Mon Feb 19 17:16:56 2007 -0600 13949:1c63549d7578

(XEN) Physical RAM map:
(XEN)   : 8000
(XEN)   0001: 8000
(XEN) End of Xen Area: 144MiB (147456KiB)
(XEN) End of RAM: 6144MiB (6291456KiB)
(XEN) boot allocator @ 3c000 - 6d000
(XEN) boot free: 0900 - 8000
(XEN) boot free: 0001 - 00018000
(XEN) total_pages: 0x000f7000
(XEN) NUMA turned off
(XEN) Faking a node at -00018000
(XEN) Domain heap initialised: DMA width 64 bits
(XEN) xenheap: 0006d000 - 0040
(XEN) xenheap: 00c46000 - 0900
(XEN) Xen Heap: 135MiB (138548KiB)
(XEN) Dom Heap: 3880MiB (3973120KiB)
(XEN) CPU[PIR:0 IPI:0 Logical:0] Hello World!
(XEN) xen_mpic_init: start
(XEN) mpic: Setting up MPIC Xen-U3-MPIC version 1.2 at f804, max 4 CPUs
(XEN) mpic: ISU size: 124, shift: 7, mask: 7f
(XEN) mpic: Initializing for 124 sources
(XEN) mpic: Setting up HT PICs workarounds for U3/U4
(XEN) mpic:   - HT:07.0 [0xf0] vendor 1022 device 7460 has 24 irqs
(XEN) xen_mpic_init: success
(XEN) requesting IPIs ...
(XEN) IPIs requested...
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing DART 0xf8033000: tbl: 0020[0x200] entries: 
0x8
(XEN) Initializing DART Model U4: ctl: 0x8000 base: 0x200 size: 0x200
(XEN) spinning up at most 16 total processors ...
(XEN) Synchronizing timebase
(XEN) CPU[PIR:1 IPI:1 Logical:1] Hello World!
(XEN) Got ack 
(XEN) score 299, offset 1000
(XEN) score 299, offset 500
(XEN) score 299, offset 250
(XEN) score 299, offset 125
(XEN) score 299, offset 62
(XEN) score 299, offset 31
(XEN) score 299, offset 15
(XEN) score 111, offset 7
(XEN) score -299, offset 3
(XEN) score -299, offset 5
(XEN) score -299, offset 6
(XEN) Min 6 (score -299), Max 7 (score 119)
(XEN) Final offset: 7 (215/300)
(XEN) Synchronizing timebase
(XEN) CPU[PIR:2 IPI:2 Logical:2] Hello World!
(XEN) Got ack 
(XEN) score 299, offset 1000
(XEN)

Re: [XenPPC] Re: xen heap size

2007-02-23 Thread Ryan Harper

* Jimi Xenidis [EMAIL PROTECTED] [2007-02-22 19:30]:
 We don't consider the RMA boundary for the Xen heap at all anymore  
 (not for a while)
 The Xen heap is calculated based on the estimated resources we'll need.
 on example is that we need to get enough HTABs for all the domain, so  
 1/64th of all of memory is part of the Xen heap size.

Hrm.  One of the items I need to address is determining how much of
dom0's memory allocation runs into the 2-4G IO hole.  One method I was
hoping might work is:


 /* overlap in pages into 2G-4G IO range (if any) */
dom0_overlap = (cpu_default_rma_order_pages() + dom0_nrpages) -
   IO_SIZE_PAGES;

It doesn't look like we can make the assumption that Xen+xenheap will
only occupy the first RMA of the platform.  

The other method I was going to look into was to allocate dom0's rma,
and then calculation would look like:

   dom0_start_mfn = page_to_mfn(d-arch.rma_base);
   dom0_overlap = (dom0_start_mfn + dom0_nrpages - rma_sz) - IO_SIZE_PAGES;
   
Any other good way to figure how much of dom0's allocation will fall
within 2-4G IO hole?

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
[EMAIL PROTECTED]

___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel

Re: [XenPPC] Re: xen heap size

2007-02-23 Thread Hollis Blanchard

On Fri, 2007-02-23 at 10:21 -0600, Ryan Harper wrote:
 
 The other method I was going to look into was to allocate dom0's rma,
 and then calculation would look like:
 
dom0_start_mfn = page_to_mfn(d-arch.rma_base);
dom0_overlap = (dom0_start_mfn + dom0_nrpages - rma_sz) -
 IO_SIZE_PAGES;

 Any other good way to figure how much of dom0's allocation will fall
 within 2-4G IO hole?

Why are you looking for another approach? What's wrong with this
solution?

-- 
Hollis Blanchard
IBM Linux Technology Center


___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel

[XenPPC] Re: xen heap size

2007-02-22 Thread Hollis Blanchard

On Thu, 2007-02-22 at 16:07 -0600, Ryan Harper wrote:

 IIRC, when dom0 boots with 192MB (the default) I usually see ~19MB of
 heap available in the boot messages on js20.  Looking at js21, I see:
 
 (XEN) Xen Heap: 135MiB (138548KiB)
 
 RMA different size on js21? 

That's an unusual size: it's slightly more than the second 64MB RMA
boundary, which seems to indicate there's a lot of wasted memory before
dom0 at 192MB. I wonder if this is related to the 4GB of memory in this
system. A more complete boot log might shed some light on it.

To answer your question, the 970MP (in JS21) supports the same RMA sizes
as 970 and 970FX (in JS20).

-- 
Hollis Blanchard
IBM Linux Technology Center


___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel

Re: [XenPPC] Re: xen heap size

2007-02-22 Thread Jimi Xenidis

We don't consider the RMA boundary for the Xen heap at all anymore  
(not for a while)

The Xen heap is calculated based on the estimated resources we'll need.
on example is that we need to get enough HTABs for all the domain, so  
1/64th of all of memory is part of the Xen heap size.


check out powerpc/memory.c: memory_init()

On Feb 22, 2007, at 5:28 PM, Hollis Blanchard wrote:


On Thu, 2007-02-22 at 16:07 -0600, Ryan Harper wrote:


IIRC, when dom0 boots with 192MB (the default) I usually see ~19MB of
heap available in the boot messages on js20.  Looking at js21, I see:

(XEN) Xen Heap: 135MiB (138548KiB)

RMA different size on js21?


That's an unusual size: it's slightly more than the second 64MB RMA
boundary, which seems to indicate there's a lot of wasted memory  
before
dom0 at 192MB. I wonder if this is related to the 4GB of memory in  
this

system. A more complete boot log might shed some light on it.

To answer your question, the 970MP (in JS21) supports the same RMA  
sizes

as 970 and 970FX (in JS20).

--
Hollis Blanchard
IBM Linux Technology Center


___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel



___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel

[XenPPC] Re: xen heap size

Re: [XenPPC] Re: xen heap size

Re: [XenPPC] Re: xen heap size

[XenPPC] Re: xen heap size

Re: [XenPPC] Re: xen heap size

5 matches

Site Navigation

Mail list logo

Footer information