All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Deegan <Tim.Deegan@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	xen-devel@lists.xensource.com, "Tian,
	Kevin" <kevin.tian@intel.com>
Subject: Re: [RFC][PATCH] 0/9 Populate-on-demand memory
Date: Tue, 30 Dec 2008 09:26:37 +0000	[thread overview]
Message-ID: <20081230092637.GB7747@york.uk.xensource.com> (raw)
In-Reply-To: <de76405a0812240746h4fca29fbg97010f76e7c14ba9@mail.gmail.com>

At 15:46 +0000 on 24 Dec (1230133560), George Dunlap wrote:
> On Wed, Dec 24, 2008 at 3:35 PM, Dan Magenheimer
> <dan.magenheimer@oracle.com> wrote:
> >> We could to allocate a new page at that point; but it's likely that
> >> the allocation will fail unless there happens to be memory lying
> >> around somewhere, not used by dom0 or any other doamin.  And if that
> >> were the case, why not just start it with that much memory to begin
> >> with?
> >
> > Actually, if dom0_mem is used rather than the default of letting
> > domain0 absorb all free memory and dole it as needed to launching
> > VMs, there will almost always be some memory lying around.
> 
> At any rate, I suppose it might not be a bad idea to *try* to allocate
> more memory in an emergency.  I'll add that to the list of
> improvements.

Please don't do this.  It's not OK for a domain to start using more
memory without the say-so of the tool stack.  Since this emergency
condition means something has gone wrong (balloon driver failed to
start) then you're probably just postponing the inevitable, and in the
meantime you might cause problems for domains that *aren't* misbehaving.

Cheers,

Tim.

-- 
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 0DZ, UK.]

  reply	other threads:[~2008-12-30  9:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23 12:55 [RFC][PATCH] 0/9 Populate-on-demand memory George Dunlap
2008-12-23 19:06 ` Dan Magenheimer
2008-12-24 13:55   ` George Dunlap
2008-12-24 14:32     ` Dan Magenheimer
2008-12-24 15:13       ` George Dunlap
2008-12-24 15:54         ` Dan Magenheimer
2008-12-24  1:46 ` Tian, Kevin
2008-12-24 14:42   ` George Dunlap
2008-12-24 15:35     ` Dan Magenheimer
2008-12-24 15:46       ` George Dunlap
2008-12-30  9:26         ` Tim Deegan [this message]
2008-12-31  1:40           ` Tian, Kevin
2009-01-02 10:03             ` Tim Deegan
2009-01-05  6:08               ` Tian, Kevin
2008-12-25  2:47       ` Tian, Kevin
2008-12-25  2:36     ` Tian, Kevin
2008-12-25  5:43       ` Han, Weidong
2008-12-25 11:45         ` Tian, Kevin
2008-12-26  0:42           ` Han, Weidong

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=20081230092637.GB7747@york.uk.xensource.com \
    --to=tim.deegan@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=kevin.tian@intel.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.