This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] [PATCH] [linux-2.6.39.x for xen] tmem: self-ballooning a

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] [linux-2.6.39.x for xen] tmem: self-ballooning and frontswap-selfshrinking
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Tue, 7 Jun 2011 17:40:12 +0100
Cc: "jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Wilk <konrad.wilk@xxxxxxxxxx>, Vasiliy G Tolstov <v.tolstov@xxxxxxxxx>, "JBeulich@xxxxxxxxxx" <JBeulich@xxxxxxxxxx>, Dushmanta Mohapatra <dmpatra@xxxxxxxxx>
Delivery-date: Tue, 07 Jun 2011 09:42:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <c9899779-063e-4191-8b11-57814199d67d@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <292df482-2d4c-4a4f-b5f4-4c808692156e@default 1307439243.775.535.camel@xxxxxxxxxxxxxxxxxxxxxx> <c9899779-063e-4191-8b11-57814199d67d@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2011-06-07 at 17:21 +0100, Dan Magenheimer wrote:
> Although you're right, as I am fresh off a 2-1/2 year odyssey of
> upstreaming cleancache, AND since this is almost certainly Xen
> specific AND since there will likely be some changes over time
> which could conceivably make this unnecessary, I would be content
> with carrying this in a Xen-only tree for the foreseeable future. 

As someone who is fresh of a 5+ year odyssey of upstreaming a Xen-only
tree into mainline I must strongly object to this approach.

We have had a long uphill battle to get ourselves to the state we are in
today and the approach you are suggesting is absolutely counter to the
philosophy we have built up whilst doing that and accepting this undoes
all of the good work up until now.

Getting stuff into a Xen tree is not an aim in and of itself but merely
a conduit towards upstream. Nothing should be going into the Xen stable
trees with the explicit aim of staying there for the foreseeable future.

If you want to run a tmem-only tree with stuff you don't intend to send
upstream yet in it then that is your prerogative, please don't ask the
rest of us to carry that burden.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>