Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932916Ab3EOUqZ (ORCPT ); Wed, 15 May 2013 16:46:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45359 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932193Ab3EOUqY (ORCPT ); Wed, 15 May 2013 16:46:24 -0400 Message-ID: <5193F3CC.8020205@redhat.com> Date: Wed, 15 May 2013 16:45:00 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 MIME-Version: 1.0 To: Dan Magenheimer CC: Konrad Wilk , Seth Jennings , Andrew Morton , Greg Kroah-Hartman , Nitin Gupta , Minchan Kim , Robert Jennings , Jenifer Hopper , Mel Gorman , Johannes Weiner , Larry Woodman , Benjamin Herrenschmidt , Dave Hansen , Joe Perches , Joonsoo Kim , Cody P Schafer , Hugh Dickens , Paul Mackerras , linux-mm@kvack.org, linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org Subject: Re: [PATCHv11 3/4] zswap: add to mm/ References: <1368448803-2089-1-git-send-email-sjenning@linux.vnet.ibm.com> <1368448803-2089-4-git-send-email-sjenning@linux.vnet.ibm.com> <15c5b1da-132a-4c9e-9f24-bc272d3865d5@default> <20130514163541.GC4024@medulla> <20130514225501.GA11956@cerebellum> <4d74f5db-11c1-4f58-97f4-8d96bbe601ac@default> <20130515185506.GA23342@phenom.dumpdata.com> <57917f43-ab37-4e82-b659-522e427fda7f@default> In-Reply-To: <57917f43-ab37-4e82-b659-522e427fda7f@default> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1405 Lines: 39 On 05/15/2013 03:35 PM, Dan Magenheimer wrote: >> From: Konrad Rzeszutek Wilk >> Subject: Re: [PATCHv11 3/4] zswap: add to mm/ >> >>> Sorry, but I don't think that's appropriate for a patch in the MM subsystem. >> >> I am heading to the airport shortly so this email is a bit hastily typed. >> >> Perhaps a compromise can be reached where this code is merged as a driver >> not a core mm component. There is a high bar to be in the MM - it has to >> work with many many different configurations. >> >> And drivers don't have such a high bar. They just need to work on a specific >> issue and that is it. If zswap ended up in say, drivers/mm that would make >> it more palpable I think. >> >> Thoughts? > > Hmmm... > > To me, that sounds like a really good compromise. Come on, we all know that is nonsense. Sure, the zswap and zbud code may not be in their final state yet, but they belong in the mm/ directory, together with the cleancache code and all the other related bits of code. Lets put them in their final destination, and hope the code attracts attention by as many MM developers as can spare the time to help improve it. -- All rights reversed -- 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/