Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1183700rwb; Wed, 9 Nov 2022 14:09:37 -0800 (PST) X-Google-Smtp-Source: AMsMyM5lX0UZ4G4/bGfB3nMfbvmFOJfGF1VG2J/26V5/rNDaP/oCccSX8gIOJZmOQqFpowYt7UPb X-Received: by 2002:a17:906:bce4:b0:7ad:d6c6:eb7c with SMTP id op4-20020a170906bce400b007add6c6eb7cmr1805199ejb.249.1668031766529; Wed, 09 Nov 2022 14:09:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668031766; cv=none; d=google.com; s=arc-20160816; b=KqbBTdgI9EeeCBaGYckdtVf8Bpn68K/jmUhReCUu5+ZlqL5xzJwBsyU5R9aAxFN2kA 0Xzj+L0COqdxz+6Ibe8Rh2EmnI1bJkYqXc7EmICOhtKXGJVGjZ85En7iLMgGbCT65lp1 zRCBlLoTfmfpJbUjkM+e1ghzG4m8DuC4Om/1k/um+8Y6Jst6GnqhThBFdQ+sqUCKM0k4 LTtQ1rpLgOJveaJFuHEJFDjWes/6KxsV7C/+Acpadgz6b5zHbv9fNlGgVGkQL+7GxQbI xihbOH9MhWO9f+QMQnx9Xuc0tarWhRY2uCPNVcJ3ewdWPi89snNGFuueLVJf3DG5t3A6 AX2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:sender:dkim-signature; bh=hp4QvFm+k+5c4Ejq+3JB+myGkwBJdStU8ykSojC7Cmw=; b=PKKow2Ukw5IhDPZW1066GGhL2sgwTtADtzTzz0oG1X0456XLwSmqoO4d1XP8v/ier7 9C8HYhRLQGypfSgyO0wvpwBEusRJqHKRuq49KIrjLuVSqTTzan0hKOIWx0a7Gyu7qk6I xfrBjiWBXUg3ihwCw4PAz+PGW32t3P7kA30HTU8jrpWKsC6Ioq/s9mfc201iqyw2wW4A PvbH0WMhWSGVxwATKiI9ah9JUTMes0/Mdo7HLU9J/prswU+1jHL4Bo3rqxX5Ava2nVNZ LwWOx4j3auj69Tu8bIOeFgzjML4cOgvzhkrWnL5ZPhMMnq2560X3zCy0FXDOY4qxLFWt KT7Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=nOFnuOnb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hv9-20020a17090760c900b007830f14fffesi17514916ejc.375.2022.11.09.14.09.04; Wed, 09 Nov 2022 14:09:26 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=nOFnuOnb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231178AbiKIVrC (ORCPT + 92 others); Wed, 9 Nov 2022 16:47:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48026 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229657AbiKIVrB (ORCPT ); Wed, 9 Nov 2022 16:47:01 -0500 Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 02CEA2FC16 for ; Wed, 9 Nov 2022 13:46:59 -0800 (PST) Received: by mail-pg1-x52a.google.com with SMTP id v3so17346223pgh.4 for ; Wed, 09 Nov 2022 13:46:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=hp4QvFm+k+5c4Ejq+3JB+myGkwBJdStU8ykSojC7Cmw=; b=nOFnuOnb+jf3mboPSPEZTlr97ZS1UEmtec/QQ51W/aJSq1f7Lx1s1OjKsgaWp/RLw1 BeYnedl3LuKsSVtSEzLLrj3t1pm57zkw2vhF2zQ5Z5RfFPLNwpuxvGNaeuR0w41wQhhD GDFx056O6bF6ze5no/gJJrkTn8xWAqm9TnT2ZBGCTmGY6fj5lKfmgL694ekGUFwUTHwW oxGQOUNpv+DscowMGBcRxZueX5sjRCn1ZB8wRh1heq+LRy9VPHpMwcqbZXIpV2oFfNnL wC9irPhoBmZ64CV32cDo4IjTk/gpqY/rixQawROsDVExART8uWqeW7lD9TdCV9KML955 mUpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=hp4QvFm+k+5c4Ejq+3JB+myGkwBJdStU8ykSojC7Cmw=; b=AyJWM+8JsI/A7KWZl+jmnyUH0u+lvA7hQXEhP8IVp7OOgifSTOdRPyNqt+xDawk+ph m6IdsDMzTZIC6X9NMzRQahR6WLgrQJitp1y64tPgtbTfiY/qFXGVph2VSZfwHqZu5jQs pR1sXQsJfLQmtTYJkB/UvkUBkAjz2kZ06xJnLZ3vaRURjKyuWZ+z+zYqo3mEqhOx6XjQ yxmLdtFQsqImosbhqDyZ/WRmPMhfDz8sLP8mGTKeRehbCZ3vvcfhTAp/hxXc/7XQsrl5 9C2S1puxbFoVE5ludBL3ZhjZUCQlA9iyKCxB2c9WLtfOCvaQtVaBsu8DHyaw5I/r1PQI 4ECw== X-Gm-Message-State: ACrzQf09gefkTbNE+qlsYtNG96wvcnLH0jghsVtQuUj6v3vFNjjcLykF TuzEV3LziNDgbyrS3RNx4Ag= X-Received: by 2002:a63:fc55:0:b0:46f:81ca:66d2 with SMTP id r21-20020a63fc55000000b0046f81ca66d2mr53636220pgk.179.1668030418339; Wed, 09 Nov 2022 13:46:58 -0800 (PST) Received: from google.com ([2620:15c:211:201:8514:5da3:d38f:7bd]) by smtp.gmail.com with ESMTPSA id 12-20020a170902c20c00b0018699e6afd8sm9498817pll.265.2022.11.09.13.46.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Nov 2022 13:46:57 -0800 (PST) Sender: Minchan Kim Date: Wed, 9 Nov 2022 13:46:56 -0800 From: Minchan Kim To: Sergey Senozhatsky Cc: Andrew Morton , Nitin Gupta , Suleiman Souhlal , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCHv5 00/13] zram: Support multiple compression streams Message-ID: References: <20221109115047.2921851-1-senozhatsky@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221109115047.2921851-1-senozhatsky@chromium.org> X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 09, 2022 at 08:50:34PM +0900, Sergey Senozhatsky wrote: > Hello, > > This series adds support for multiple compression streams. > The main idea is that different compression algorithms have different > characteristics and zram may benefit when it uses a combination of > algorithms: a default algorithm that is faster but have lower > compression rate and a secondary algorithm that can use higher > compression rate at a price of slower compression/decompression. > > There are several use-case for this functionality: > > - huge pages re-compression: zstd or deflate can successfully > compress huge pages (~50% of huge pages on my synthetic ChromeOS > tests), IOW pages that lzo was not able to compress. > > - idle pages re-compression: idle/cold pages sit in the memory > and we may reduce zsmalloc memory usage if we recompress those > idle pages. > > User-space has a number of ways to control the behavior > and impact of zram recompression: what type of pages should be > recompressed, size watermarks, etc. Please refer to documentation > patch. > > v5: > -- Addressed (very valuable) review feedback from Minchan > -- Extended documentation > -- We now do chain recompression, tryin algos in order of their priority > -- Support up to 4 compression streams > -- Added named parameters to recomp_algorithm and recompress sysfs knobs > -- Cherry-picked patch from Alexey > -- Store algo priority in mete flags > -- Renamed some fo the flags > -- Added incompressible bit to block state output > -- Added incompressible writeback > -- etc. > > v4: > -- added IS_ERR_VALUE patch (Andrew) > -- documented SIZE units (bytes) (Andrew) > -- re-phrased writeback BIO error comment (Andrew) > -- return zs_malloc() error code from zram_recompress() > -- do not lose zram_recompress() error in recompress_store() > -- corrected a typo > -- fixed previous rebase errors > -- rebased the series > > v3: > -- conditionally reschedule during recompression loop so that > we don't stall RCU grace periods > -- fixed a false-positive WARN_ON > > v2: > -- rebased > -- mark completely incompressible pages (neither default nor secondary > algorithm can compress them) with a new flag so that we don't attempt > to recompress them all the time > > Alexey Romanov (1): > zram: add size class equals check into recompression > > Sergey Senozhatsky (12): > zram: Preparation for multi-zcomp support > zram: Add recompression algorithm sysfs knob > zram: Factor out WB and non-WB zram read functions > zram: Introduce recompress sysfs knob > zram: Add recompress flag to read_block_state() > zram: Clarify writeback_store() comment > zram: Use IS_ERR_VALUE() to check for zs_malloc() errors > zram: remove redundant checks from zram_recompress() > zram: Add algo parameter support to zram_recompress() > documentation: Add zram recompression documentation > zram: add incompressible writeback > zram: Add incompressible flag to read_block_state() > > Documentation/admin-guide/blockdev/zram.rst | 100 +++- > drivers/block/zram/Kconfig | 9 + > drivers/block/zram/zcomp.c | 6 +- > drivers/block/zram/zcomp.h | 2 +- > drivers/block/zram/zram_drv.c | 604 +++++++++++++++++--- > drivers/block/zram/zram_drv.h | 22 +- > include/linux/zsmalloc.h | 2 + > mm/zsmalloc.c | 21 + > 8 files changed, 685 insertions(+), 81 deletions(-) Acked-by: Minchan Kim Thanks!