From: George Dunlap <george.dunlap@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] PoD: Handle operations properly when domain is dying
Date: Thu, 12 Nov 2009 10:56:35 +0000 [thread overview]
Message-ID: <4AFBE9E3.50306@eu.citrix.com> (raw)
In-Reply-To: <3fc04a2c-ed3a-4bdf-a02b-313a2a70f068@default>
Dan Magenheimer wrote:
> I understand that from your (developer's) point of view
> but 99% or more of your customers won't know what a p2m
> table is or what populating it means and will assume
> (as I did earlier), since this is a memory-related
> feature, that "populate" refers to utilizing RAM.
>
Since almost all the code referring to PoD is in a place that only a
devloper should look (in the hypervisor, and a little bit in the hvm
domain builder), I think the naming (at least internally) is
appropriate. One could imagine "shadow memory" being mis-interpreted in
a similar fashion. :-)
PoD is only one piece of the puzzle required to allow booting
pre-ballooned. If you feel like we need a name "marketing name" for the
whole feature to put in annoucements and changelogs, feel free to
suggest one. :-)
In XenServer, the whole thing will come under the umbrella of "Dynamic
Memory Control".
> I guess that makes sense in the Windows world where "distros"
> can be counted on one or two hands.
>
My guess is that Linux as a whole will have much less variance than
Windows. But we're not testing HVM Linux ATM.
-George
next prev parent reply other threads:[~2009-11-12 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 15:08 [PATCH] PoD: Handle operations properly when domain is dying George Dunlap
2009-11-11 15:26 ` Dan Magenheimer
2009-11-11 15:42 ` George Dunlap
2009-11-11 16:53 ` Dan Magenheimer
2009-11-11 17:13 ` Keir Fraser
2009-11-11 17:15 ` George Dunlap
2009-11-11 17:58 ` Dan Magenheimer
2009-11-11 22:49 ` George Dunlap
2009-11-11 23:34 ` Dan Magenheimer
2009-11-12 10:56 ` George Dunlap [this message]
2009-11-11 18:12 ` Dave Scott
2009-11-11 18:27 ` Dan Magenheimer
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=4AFBE9E3.50306@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=dan.magenheimer@oracle.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.