Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936119Ab3DJA6H (ORCPT ); Tue, 9 Apr 2013 20:58:07 -0400 Received: from LGEMRELSE6Q.lge.com ([156.147.1.121]:45567 "EHLO LGEMRELSE6Q.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762735Ab3DJA6F (ORCPT ); Tue, 9 Apr 2013 20:58:05 -0400 X-AuditID: 9c930179-b7b2aae000000518-0c-5164b91911fb Date: Wed, 10 Apr 2013 09:58:01 +0900 From: Minchan Kim To: Seth Jennings Cc: Dan Magenheimer , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Hugh Dickins , Nitin Gupta , Konrad Rzeszutek Wilk , Shaohua Li , Bob Liu , Shuah Khan Subject: Re: zsmalloc defrag (Was: [PATCH] mm: remove compressed copy from zram in-memory) Message-ID: <20130410005801.GH6836@blaptop> References: <1365400862-9041-1-git-send-email-minchan@kernel.org> <20130409012719.GB3467@blaptop> <20130409013606.GC3467@blaptop> <51647F94.6000907@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51647F94.6000907@linux.vnet.ibm.com> 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: 2624 Lines: 67 Hi Seth, On Tue, Apr 09, 2013 at 03:52:36PM -0500, Seth Jennings wrote: > On 04/08/2013 08:36 PM, Minchan Kim wrote: > > On Tue, Apr 09, 2013 at 10:27:19AM +0900, Minchan Kim wrote: > >> Hi Dan, > >> > >> On Mon, Apr 08, 2013 at 09:32:38AM -0700, Dan Magenheimer wrote: > >>>> From: Minchan Kim [mailto:minchan@kernel.org] > >>>> Sent: Monday, April 08, 2013 12:01 AM > >>>> Subject: [PATCH] mm: remove compressed copy from zram in-memory > >>> > >>> (patch removed) > >>> > >>>> Fragment ratio is almost same but memory consumption and compile time > >>>> is better. I am working to add defragment function of zsmalloc. > >>> > >>> Hi Minchan -- > >>> > >>> I would be very interested in your design thoughts on > >>> how you plan to add defragmentation for zsmalloc. In > >> > >> What I can say now about is only just a word "Compaction". > >> As you know, zsmalloc has a transparent handle so we can do whatever > >> under user. Of course, there is a tradeoff between performance > >> and memory efficiency. I'm biased to latter for embedded usecase. > >> > >> And I might post it because as you know well, zsmalloc > > > > Incomplete sentense, > > > > I might not post it until promoting zsmalloc because as you know well, > > zsmalloc/zram's all new stuffs are blocked into staging tree. > > Even if we could add it into staging, as you know well, staging is where > > every mm guys ignore so we end up needing another round to promote it. sigh. > > Yes. The lack of compaction/defragmentation support in zsmalloc has not > been raised as an obstacle to mainline acceptance so I think we should > wait to add new features to a yet-to-be accepted codebase. > > Also, I think this feature is more important to zram than it is to > zswap/zcache as they can do writeback to free zpages. In other words, > the fragmentation is a transient issue for zswap/zcache since writeback > to the swap device is possible. Other benefit derived from compaction work is that we can pick a zpage from zspage and move it into somewhere. It means core mm could control pages in zsmalloc freely. > > Thanks, > Seth > > -- > 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 -- 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/