[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A5660CB.5080607@redhat.com>
Date: Thu, 09 Jul 2009 17:27:39 -0400
From: Rik van Riel <riel@...hat.com>
To: Dan Magenheimer <dan.magenheimer@...cle.com>
CC: Anthony Liguori <anthony@...emonkey.ws>,
linux-kernel@...r.kernel.org, npiggin@...e.de, akpm@...l.org,
jeremy@...p.org, xen-devel@...ts.xensource.com,
tmem-devel@....oracle.com, alan@...rguk.ukuu.org.uk,
linux-mm@...ck.org, kurt.hackel@...cle.com,
Rusty Russell <rusty@...tcorp.com.au>,
dave.mccracken@...cle.com, Marcelo Tosatti <mtosatti@...hat.com>,
sunil.mushran@...cle.com, Avi Kivity <avi@...hat.com>,
Schwidefsky <schwidefsky@...ibm.com>, chris.mason@...cle.com,
Balbir Singh <balbir@...ux.vnet.ibm.com>
Subject: Re: [RFC PATCH 0/4] (Take 2): transcendent memory ("tmem") for Linux
Dan Magenheimer wrote:
> I'm not saying either one is bad or good -- and I'm sure
> each can be adapted to approximately deliver the value
> of the other -- they are just approaching the same problem
> from different perspectives.
Indeed. Tmem and auto-ballooning have a simple mechanism,
but the policy required to make it work right could well
be too complex to ever get right.
CMM2 has a more complex mechanism, but the policy is
absolutely trivial.
CMM2 and auto-ballooning seem to give about similar
performance gains on zSystem.
I suspect that for Xen and KVM, we'll want to choose
for the approach that has the simpler policy, because
relying on different versions of different operating
systems to all get the policy of auto-ballooning or
tmem right is likely to result in bad interactions
between guests and other intractable issues.
--
All rights reversed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists