From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx141.postini.com [74.125.245.141]) by kanga.kvack.org (Postfix) with SMTP id 1913B6B0096 for ; Tue, 11 Sep 2012 22:37:14 -0400 (EDT) Date: Wed, 12 Sep 2012 11:39:14 +0900 From: Minchan Kim Subject: Query of zram/zsmalloc promotion Message-ID: <20120912023914.GA31715@bbox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-linux-mm@kvack.org List-ID: To: Jens Axboe , Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Nitin Gupta , Seth Jennings , Dan Magenheimer , Konrad Rzeszutek Wilk , Greg Kroah-Hartman Hi all, I would like to promote zram/zsmalloc from staging tree. I already tried it https://lkml.org/lkml/2012/8/8/37 but I didn't get any response from you guys. I think zram/zsmalloc's code qulity is good and they are used for many embedded vendors for a long time. So it's proper time to promote them. The zram should put on under driver/block/. I think it's not arguable but the issue is which directory we should keep *zsmalloc*. Now Nitin want to keep it with zram so it would be in driver/blocks/zram/ But I don't like it because zsmalloc touches several fields of struct page freely(and AFAIRC, Andrew had a same concern with me) so I want to put it under mm/. In addtion, now zcache use it, too so it's rather awkward if we put it under dirver/blocks/zram/. So questions. To Andrew: Is it okay to put it under mm/ ? Or /lib? To Jens: Is it okay to put zram under drvier/block/ If you are okay, I will start sending patchset after I sort out zsmalloc's location issue. -- Kind regards, Minchan Kim -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org