From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Konrad Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xen.org
Subject: RE: [PATCH] xen: tmem: selfballooning should be enabled when xen tmem is enabled
Date: Wed, 21 Nov 2012 07:26:58 -0800 (PST) [thread overview]
Message-ID: <3b3b72db-32fd-446c-9971-e119a8993b3d@default> (raw)
In-Reply-To: <20121121024753.GB11912@konrad-lan.dumpdata.com>
> From: Konrad Rzeszutek Wilk
> Sent: Tuesday, November 20, 2012 7:48 PM
> To: Dan Magenheimer
> Cc: linux-kernel@vger.kernel.org; xen-devel@lists.xen.org
> Subject: Re: [PATCH] xen: tmem: selfballooning should be enabled when xen tmem is enabled
>
> On Tue, Nov 20, 2012 at 02:42:18PM -0800, Dan Magenheimer wrote:
> > Konrad: Any chance this can get in for the upcoming window?
> > (Or is it enough of a bug fix that it can go in at an -rcN?)
>
> Lets do it in the next merge window. About now I am comfortable
> only with regression fixes.
OK, thanks!
> > It was just pointed out to me that some kernels have
> > cleancache and frontswap and xen_tmem enabled but NOT
> > xen_selfballooning! While this configuration should be
> > possible, nearly all kernels that have CONFIG_XEN_TMEM=y should
> > also have CONFIG_XEN_SELFBALLOONING=y, since Transcendent
> > Memory (tmem) for Xen has very limited value without
> > selfballooning.
> >
> > This is probably a result of a Kconfig mistake fixed I think
> > by the patch below. Note that the year-old Oracle UEK2 kernel
> > distro has both CONFIG_XEN_TMEM and CONFIG_XEN_SELFBALLOONING
> > enabled, as does a Fedora 17 kernel update (3.6.6-1.fc17), so
> > the combination should be well tested. Also, Xen tmem (and thus
> > selfballooning) are currently only enabled when a kernel boot
> > parameter is supplied so there is no runtime impact without
> > that boot parameter.
> >
> > Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
> >
> > diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
> > index d4dffcd..b5f02f3 100644
> > --- a/drivers/xen/Kconfig
> > +++ b/drivers/xen/Kconfig
> > @@ -10,9 +10,9 @@ config XEN_BALLOON
> > return unneeded memory to the system.
> >
> > config XEN_SELFBALLOONING
> > - bool "Dynamically self-balloon kernel memory to target"
> > - depends on XEN && XEN_BALLOON && CLEANCACHE && SWAP && XEN_TMEM
> > - default n
> > + bool
> > + depends on XEN_BALLOON && SWAP
> > + default y if XEN_TMEM
> > help
> > Self-ballooning dynamically balloons available kernel memory driven
> > by the current usage of anonymous memory ("committed AS") and
next prev parent reply other threads:[~2012-11-21 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 22:42 [PATCH] xen: tmem: selfballooning should be enabled when xen tmem is enabled Dan Magenheimer
2012-11-21 2:47 ` Konrad Rzeszutek Wilk
2012-11-21 15:26 ` Dan Magenheimer [this message]
2012-11-21 8:21 ` [Xen-devel] " Jan Beulich
2012-11-21 15:42 ` Dan Magenheimer
2012-11-21 15:54 ` Jan Beulich
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=3b3b72db-32fd-446c-9971-e119a8993b3d@default \
--to=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xen.org \
/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