From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xl.cfg: document the maxmem= option
Date: Fri, 4 May 2012 22:18:02 +0200 [thread overview]
Message-ID: <20120504201802.GA16466@aepfle.de> (raw)
In-Reply-To: <20120504194222.GA28634@phenom.dumpdata.com>
On Fri, May 04, Konrad Rzeszutek Wilk wrote:
> On Fri, May 04, 2012 at 09:31:42PM +0200, Olaf Hering wrote:
> > # HG changeset patch
> > # User Olaf Hering <olaf@aepfle.de>
> > # Date 1336159720 -7200
> > # Node ID c414728d0d12f1c3e416e40cceefca2f0b00578e
> > # Parent 8f556a70ae0bef47e242f9e7be0a054769fc8277
> > xl.cfg: document the maxmem= option
> >
> > Signed-off-by: Olaf Hering <olaf@aepfle.de>
> >
> > diff -r 8f556a70ae0b -r c414728d0d12 docs/man/xl.cfg.pod.5
> > --- a/docs/man/xl.cfg.pod.5
> > +++ b/docs/man/xl.cfg.pod.5
> > @@ -484,6 +484,14 @@ are not using hardware assisted paging (
> > mode) and your guest workload consists of a a very large number of
> > similar processes then increasing this value may improve performance.
> >
> > +=item B<maxmem=MBYTES>
> > +
> > +Specifies the maximum amount of memory the HVM guest can ever see.
>
> Isn't it also for PV guests (though without the PoD functionality)?
Now that I look again at libxl__build_pre(), it appearently does also
something for PV guests. I will resend the patch.
Thanks for the review.
Olaf
next prev parent reply other threads:[~2012-05-04 20:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 19:31 [PATCH] xl.cfg: document the maxmem= option Olaf Hering
2012-05-04 19:42 ` Konrad Rzeszutek Wilk
2012-05-04 20:18 ` Olaf Hering [this message]
2012-05-06 9:35 ` Ian Campbell
2012-05-07 13:06 ` Olaf Hering
2012-05-07 16:37 ` Dan Magenheimer
2012-05-08 12:41 ` Ian Campbell
2012-05-08 15:40 ` Dan Magenheimer
-- strict thread matches above, loose matches on Subject: below --
2012-05-31 15:04 Olaf Hering
2012-06-01 11:05 ` Ian Campbell
2012-06-01 14:59 ` Olaf Hering
2012-06-01 14:55 Olaf Hering
2012-06-06 12:54 ` Ian Campbell
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=20120504201802.GA16466@aepfle.de \
--to=olaf@aepfle.de \
--cc=konrad.wilk@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 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).