All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] increase initial memory reservation for stubdom based HVM domains
Date: Thu, 15 Jan 2009 17:08:29 +0000	[thread overview]
Message-ID: <496F6D8D.9050302@eu.citrix.com> (raw)
In-Reply-To: <C5951D24.21023%keir.fraser@eu.citrix.com>

Keir Fraser wrote:

> On 15/01/2009 16:46, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
> wrote:
> 
>> this patch requests 32 additional MB of free RAM from dom0 when an HVM
>> domain is started, if the device model for the domain is provided by a
>> stubdom.
>> This way there is no risk that a stubdom fails to populate the videoram
>> because the RAM freed for the videoram by dom0 has already been used to
>> create the stubdom.
> 
> Does this mean you're giving up on 'properly' fixing the auto ballooner? :-)
> 
> At least the +32 needs a comment. Perhaps abstraction into a function or
> variable as well as a comment. Is the value 32 as arbitrary as it seems?
> 

This fix is not as bad as it seems: I am only increasing the memory
freed by the autoballoner when a stubdom based HVM domain is created, in
order to also take into account the memory used by the stubdom.
In facts 32MB is exactly the size currently needed by a stubdom, it can
probably be reduced, but I preferred making one step at a time.
The memory actually used to create the HVM domain is still the same as
before.

  reply	other threads:[~2009-01-15 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 16:46 [PATCH] increase initial memory reservation for stubdom based HVM domains Stefano Stabellini
2009-01-15 17:04 ` Keir Fraser
2009-01-15 17:08   ` Stefano Stabellini [this message]
2009-01-15 17:34     ` Keir Fraser
2009-01-15 17:44       ` Samuel Thibault
2009-01-15 17:59         ` Stefano Stabellini
2009-01-15 18:34           ` Trolle Selander
2009-01-15 17:42   ` Samuel Thibault

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496F6D8D.9050302@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.