From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com, Daniel Kiper <dkiper@net-space.pl>,
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Subject: RE: Linux mainstream balloon driver fails to grow memory= -> maxmem=
Date: Wed, 25 Aug 2010 15:44:55 -0700 (PDT) [thread overview]
Message-ID: <062d3fa7-cd0c-41b9-b8f8-ceaa9b55e3db@default> (raw)
In-Reply-To: <be6bb3c0-28dd-4faa-9386-e3a99c99c733@default>
> So if Daniel's stuff works along with tmem, I'm not too bothered about
> fixing this known difference between 2.6.18-xen and mainstream.
> And IIRC the maxmem= parameter is required for PoD to work for Windows
> also. IOW, this should probably be documented (any ideas where?)
> but the "old way" may best be left to obsolesce with 2.6.18-xen.
Hmmm... I spoke too soon. We apparently have a number of customers
that use maxmem and would be upset if the functionality goes away.
> > There's a couple of experiments floating around in the tree to try to
> > honour maxmem, but they're somewhat rotted. Its probably worth
> > trying to resurrect them though.
If you can send more information about the "experiments",
I may be able to take a look fairly soon (unless Daniel Kiper
is already looking into it). Since the support is currently
missing from RHEL6 beta, future customers using RHEL6 as a
Xen PV guest may get very confused by what might appear to
them as a tools or Xen bug.
Thanks,
Dan
prev parent reply other threads:[~2010-08-25 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 23:49 Linux mainstream balloon driver fails to grow memory= -> maxmem= Dan Magenheimer
2010-08-24 0:50 ` Jeremy Fitzhardinge
2010-08-24 2:11 ` Dan Magenheimer
2010-08-24 11:29 ` Vasiliy G Tolstov
2010-08-24 19:56 ` Daniel Kiper
2010-08-24 20:22 ` Vasiliy G Tolstov
2010-08-25 22:44 ` Dan Magenheimer [this message]
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=062d3fa7-cd0c-41b9-b8f8-ceaa9b55e3db@default \
--to=dan.magenheimer@oracle.com \
--cc=dkiper@net-space.pl \
--cc=jeremy@goop.org \
--cc=v.tolstov@selfip.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).