From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752839AbcBVCEg (ORCPT ); Sun, 21 Feb 2016 21:04:36 -0500 Received: from mail-pf0-f173.google.com ([209.85.192.173]:35592 "EHLO mail-pf0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752594AbcBVCEf (ORCPT ); Sun, 21 Feb 2016 21:04:35 -0500 Date: Mon, 22 Feb 2016 11:05:47 +0900 From: Sergey Senozhatsky To: Sergey Senozhatsky Cc: Minchan Kim , Sergey Senozhatsky , Andrew Morton , Joonsoo Kim , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH v2 2/3] zram: use zs_get_huge_class_size_watermark() Message-ID: <20160222020547.GC488@swordfish> References: <1456061274-20059-1-git-send-email-sergey.senozhatsky@gmail.com> <1456061274-20059-3-git-send-email-sergey.senozhatsky@gmail.com> <20160222000436.GA21710@bbox> <20160222004047.GA4958@swordfish> <20160222012758.GA27829@bbox> <20160222015912.GA488@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160222015912.GA488@swordfish> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (02/22/16 10:59), Sergey Senozhatsky wrote: [..] > > > > Having said that, I agree your claim that uncompressible pages > > > > are pain. I want to handle the problem as multiple-swap apparoach. > > > > > > zram is not just for swapping. as simple as that. > > > > Yes, I mean if we have backing storage, we could mitigate the problem > > like the mentioned approach. Otherwise, we should solve it in allocator > > itself and you suggested the idea and I commented first step. > > What's the problem, now? > > well, I didn't say I have problems. > so you want a backing device that will keep only 'bad compression' > objects and use zsmalloc to keep there only 'good compression' objects? > IOW, no huge classes in zsmalloc at all? hm, in the worst case we can have _for example_ 80+% of writes to be 'bad compression'. that turns zsmalloc into a 3rd wheel, and makes it almost unneeded. hm, may be it's better for now to fix zsmalloc-zram pair. -ss