Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932743Ab3HNQSF (ORCPT ); Wed, 14 Aug 2013 12:18:05 -0400 Received: from mail-pb0-f42.google.com ([209.85.160.42]:55381 "EHLO mail-pb0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759999Ab3HNQSB (ORCPT ); Wed, 14 Aug 2013 12:18:01 -0400 Date: Thu, 15 Aug 2013 01:17:53 +0900 From: Minchan Kim To: Luigi Semenzato Cc: Greg Kroah-Hartman , Andrew Morton , Jens Axboe , Seth Jennings , Nitin Gupta , Konrad Rzeszutek Wilk , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Pekka Enberg , Mel Gorman Subject: Re: [PATCH v6 0/5] zram/zsmalloc promotion Message-ID: <20130814161753.GB2706@gmail.com> References: <1376459736-7384-1-git-send-email-minchan@kernel.org> 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) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1760 Lines: 42 Hi Luigi, On Wed, Aug 14, 2013 at 08:53:31AM -0700, Luigi Semenzato wrote: > During earlier discussions of zswap there was a plan to make it work > with zsmalloc as an option instead of zbud. Does zbud work for AFAIR, it was not an optoin but zsmalloc was must but there were several objections because zswap's notable feature is to dump compressed object to real swap storage. For that, zswap needs to store bounded objects in a zpage so that dumping could be bounded, too. Otherwise, it could encounter OOM easily. > compression factors better than 2:1? I have the impression (maybe > wrong) that it does not. In our use of zram (Chrome OS) typical Since zswap changed allocator from zsmalloc to zbud, I didn't follow because I had no interest of low compressoin ratio allocator so I have no idea of status of zswap at a moment but I guess it would be still 2:1. > overall compression ratios are between 2.5:1 and 3:1. We would hate > to waste that memory if we switch to zswap. If you have real swap storage, zswap might be better although I have no number but real swap is money for embedded system and it has sudden garbage collection on firmware side if we use eMMC or SSD so that it could affect system latency. Morever, if we start to use real swap, maybe we should encrypt the data and it would be severe overhead(CPU and Power). And what I am considering after promoting for zram feature is asynchronous I/O and it's possible because zram is block device. 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/