[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] xl.cfg: document the maxmem= option
> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx] > Sent: Sunday, May 06, 2012 3:36 AM > To: Olaf Hering > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Konrad Rzeszutek Wilk > Subject: Re: [Xen-devel] [PATCH] xl.cfg: document the maxmem= option > > On Fri, 2012-05-04 at 16:18 -0400, Olaf Hering wrote: > > 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@xxxxxxxxx> > > > > # Date 1336159720 -7200 > > > > # Node ID c414728d0d12f1c3e416e40cceefca2f0b00578e > > > > # Parent 8f556a70ae0bef47e242f9e7be0a054769fc8277 > > > > xl.cfg: document the maxmem= option > > > > > > > > Signed-off-by: Olaf Hering <olaf@xxxxxxxxx> > > > > > > > > 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. can _ever_ see... What about guest OS's that support hotplug memory? Also, a subtle point, but is this the maximum physical address that will contain read/write pages or the maximum amount of RAM that the guest OS should be prepared to map as read/writeable (e.g. after subtracting off reserved e820 ranges) or ??? _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |