Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756662Ab2HGAml (ORCPT ); Mon, 6 Aug 2012 20:42:41 -0400 Received: from LGEMRELSE6Q.lge.com ([156.147.1.121]:57401 "EHLO LGEMRELSE6Q.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751457Ab2HGAmj (ORCPT ); Mon, 6 Aug 2012 20:42:39 -0400 X-AuditID: 9c930179-b7bdcae000003d91-32-5020647e1da6 Date: Tue, 7 Aug 2012 09:44:05 +0900 From: Minchan Kim To: Dan Magenheimer Cc: Pekka Enberg , Konrad Wilk , Greg Kroah-Hartman , devel@driverdev.osuosl.org, Seth Jennings , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Konrad Rzeszutek Wilk , Andrew Morton , Robert Jennings , Nitin Gupta Subject: Re: [PATCH 0/4] promote zcache from staging Message-ID: <20120807004405.GA19515@bbox> References: <5016DE4E.5050300@linux.vnet.ibm.com> <20120731155843.GP4789@phenom.dumpdata.com> <20120731161916.GA4941@kroah.com> <20120731175142.GE29533@phenom.dumpdata.com> <20120806003816.GA11375@bbox> <041cb4ce-48ae-4600-9f11-d722bc03b9cc@default> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: AAAAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1581 Lines: 42 Hi Dan, On Mon, Aug 06, 2012 at 09:21:22AM -0700, Dan Magenheimer wrote: > > From: Pekka Enberg [mailto:penberg@kernel.org] > > Subject: Re: [PATCH 0/4] promote zcache from staging > > > > On Mon, Aug 6, 2012 at 6:24 PM, Dan Magenheimer > > wrote: > > > IMHO, the fastest way to get the best zcache into the kernel and > > > to distros and users is to throw away the "demo" version, move forward > > > to a new solid well-designed zcache code base, and work together to > > > build on it. There's still a lot to do so I hope we can work together. > > > > I'm not convinced it's the _fastest way_. > > I guess I meant "optimal", combining "fast" and "best". > > > You're effectively > > invalidating all the work done under drivers/staging so you might end up > > in review limbo with your shiny new code... > > Fixing the fundamental design flaws will sooner or later invalidate > most (or all) of the previous testing/work anyway, won't it? Since > any kernel built with staging is "tainted" already, I feel like now > is a better time to make a major design transition. > > I suppose: > > (E) replace "demo" zcache with new code base and keep it > in staging for another cycle I go for (E). Please send your refactoring code as formal patch. Thanks. -- Kind regards, Minchan Kim -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/