All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "James (song wei)" <jsong@novell.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Memory pool for paravirtual guest in memory over 128G system
Date: Tue, 01 Dec 2009 13:33:25 +0000	[thread overview]
Message-ID: <C73ACBA5.337D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <26570558.post@talk.nabble.com>

On 30/11/2009 07:43, "James (song wei)" <jsong@novell.com> wrote:

> the main idea of this patch is:
> 1) The admin sets aside some memory below 128G for 32-bit paravirtual domain
> creation (via dom0_mem=-<value> in kernel comand line).
> 2) The admin also explicitly states to the tools (i..e xend) how much memory
> is supposed to be left untouched by 64-bit domains
> 3) If a 32-bit pv DomU gets created, no ballooning ought to be necessary
> (since if it is, no guarantee can be made about the address range of the
> memory ballooned out), and memory gets allocated from the reserved range.
> 4) Upon 64-bit (or 32-bit HVM or HVM) DomU creation, the tools determine the
> amount of memory to be ballooned out of Dom0 by adding the amount needed for
> the new guest and the amount still in the reserved pool (and then of course
> subtracting the total amount of memory the hypervisor has available for
> guest use).
> 
> Signed-off-by: james song (wei)<jsong@novell.com>

The patch is corrupted (line wrapped). You need to re-send as an attachment.
Please include the changeset comment and sign-off again.

 -- Keir

  reply	other threads:[~2009-12-01 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30  7:43 [PATCH] Memory pool for paravirtual guest in memory over 128G system James (song wei)
2009-12-01 13:33 ` Keir Fraser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-02  5:38 James Song

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=C73ACBA5.337D%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=jsong@novell.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.