Re: [XenPPC] Re: xen heap size
* 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
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
Re: [XenPPC] Re: xen heap size
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
