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/
Home Products Support Community News


Re: [Xen-devel] is paging_new_log_dirty_page alloc page harmfull?

To: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] is paging_new_log_dirty_page alloc page harmfull?
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Mon, 7 Mar 2011 16:16:55 +0000
Cc: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 07 Mar 2011 08:18:37 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110307090457.GB28166@xxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BLU157-w46D6341FE9D3E2BE2DBB33DAC20@xxxxxxx> <20110304111659.GA23341@xxxxxxxxxxxxxxxxxxxxxxx> <BLU157-w51C8544F3689C36FACC318DAC70@xxxxxxx> <20110307090457.GB28166@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Mon, 7 Mar 2011, Tim Deegan wrote:
> At 03:41 +0000 on 07 Mar (1299469316), MaoXiaoyun wrote:
> > Thanks Tim.
> >
> > Do you have suggestion on how many memory I should reserved, is 512M
> > enough?  There is a balloon daemon process in dom0 do the memory
> > management, the striaght way to reserve memory is after recycle memory
> > form domains which no need memory , then give the memory to those
> > domains who need memory. What do you think of this?
> Maybe the people who have been working on the toolstack can answer this
> one - 512MiB free sounds like more than enough to me but I could be
> wrong. 

give a look at how freememslack is set in

free_mem_slack_kb = (uint32_t) (PAGE_TO_MEMKB(physinfo.total_pages) -
/* From empirical measurements the free_mem_slack shouldn't be more
 * than 15% of the total memory present on the system. */
if (free_mem_slack_kb > PAGE_TO_MEMKB(physinfo.total_pages) * 0.15)
    free_mem_slack_kb = PAGE_TO_MEMKB(physinfo.total_pages) * 0.15;
libxl__xs_write(gc, t, free_mem_slack_path, "%"PRIu32, free_mem_slack_kb);

the memory left free in the system is never more than 15% of the total
memory available and is calculated as the difference between
physinfo.total_pages (total pages in the system) and info.current_memkb
(memory currently used by dom0 at boot).

Xen-devel mailing list