From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Daniel Kiper <dkiper@net-space.pl>,
jeremy@goop.org, xen-devel@lists.xensource.com,
Ian Campbell <Ian.Campbell@citrix.com>,
JBeulich@novell.com
Subject: Re: [PATCH v3] [linux-3.0+ for xen] tmem: self-ballooning and frontswap-selfshrinking
Date: Thu, 30 Jun 2011 17:50:10 -0400 [thread overview]
Message-ID: <20110630215009.GA18218@dumpdata.com> (raw)
In-Reply-To: <426e12fd-fdba-4f83-9e9f-8832aaa5147e@default>
> ("tmem") functionality that complement cleancache and frontswap. Both
> use control theory to dynamically adjust and optimize memory utilization.
> Selfballooning controls the in-kernel Xen balloon driver, targeting a goal
> value (vm_committed_as), thus pushing less frequently used clean
> page cache pages (through the cleancache code) into Xen tmem where
> Xen can balance needs across all VMs residing on the physical machine.
Can this be used by KVM or HyperV code? Can it be made generic? If so, why not?
If only Xen can use this, what would it entail for other balloon drivers
to use this? Or is it that they really don't need to b/c none of them
use the clean cache code?
> Frontswap-selfshrinking controls the number of pages in frontswap,
> driving it towards zero (effectively doing a partial swapoff) when
> in-kernel memory pressure subsides, freeing up RAM for other VMs.
next prev parent reply other threads:[~2011-06-30 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 20:15 [PATCH v3] [linux-3.0+ for xen] tmem: self-ballooning and frontswap-selfshrinking Dan Magenheimer
2011-06-30 21:50 ` Konrad Rzeszutek Wilk [this message]
2011-06-30 22:08 ` Dan Magenheimer
2011-06-30 22:19 ` Konrad Rzeszutek Wilk
2011-06-30 22:43 ` Dan Magenheimer
2011-07-04 13:31 ` Daniel Kiper
2011-07-04 20:06 ` Dan Magenheimer
2011-07-05 17:55 ` Daniel Kiper
2011-07-05 19:38 ` Dan Magenheimer
2011-07-06 9:39 ` Daniel Kiper
[not found] <426e12fd-fdba-4f83-9e9f-8832aaa5147e@default20110630215009.GA18218@dumpdata.com>
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=20110630215009.GA18218@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@novell.com \
--cc=dan.magenheimer@oracle.com \
--cc=dkiper@net-space.pl \
--cc=jeremy@goop.org \
--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.