Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp4793934ybp; Mon, 14 Oct 2019 10:06:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqzDbH5RbCkpH38Lq8ou0I0UVGL/P6EN4joBwowTdcn/2CzaWMT4wNZqRbWFsM178rRrz4U4 X-Received: by 2002:a50:f742:: with SMTP id j2mr28929967edn.253.1571072808835; Mon, 14 Oct 2019 10:06:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571072808; cv=none; d=google.com; s=arc-20160816; b=sYEDbaRQk1UdSoXV+4zACD6Cvh/6BAhgbEOddhLyLzjdnpeRphaG9ZnYBog3iGzl7m ka6gagpAHX+/U9e30hpPyurcYCQW4XME5ZnymteuGt8kA0AvxNh03ctKWMw43CZC3lc6 NLs2X8nB4IbGKrUu8RvRmxaF961+DMjIoLW1a5JY5FDGu/VBCrAP4HjW3r0zJw6I4WE2 r2D8qv9fS/cpPi3EmBm+6ymelu3yTBsIfJPsS9d7vszGCGqSxIBfRn69sD1TQe10w6LO 0ub3NQPf5SfBUNBGsW1v9Ny+ByfCk6Fnx598hCjV9SupPFQcMUuueGJ6O65XzRvWjy9A fFXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=yGcjVdTMGCzNncU46yGhvMqxXtCQHqNYV1cWFlBhCFE=; b=Li625ldzSw+/0r1WK9fJLbegrqf6qjKkED6LkgVkXJGWfjbZp9zZx63xHxe9yM2nv6 6x3QTnSp3mE+pnrvZVhX+3iQDZWZzAGqt0vsZw6TrCiXcrlOlkqJ5mH6NAwymMydmCA/ AP+XHff0ye1mv03Z8Hp21k0KskrvgIzslT30g4g4uGJ5WuFUBXX2Hk+Kim+ny3lsVyQ6 XZKeChpw1A/+fuYpFmmX8r4Dz9ajo7duyq0uKBMy25x/BlkEeC8ndx4RbNftE0mVjt0/ FUsTXxqAVTNnWVfJkGrOUx8btz7xO4c7Qh7Eu10AknmEfBmZVwGMDEZmuf4NN/t5yEat NWPA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=UTqEumcJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w26si11625708eda.438.2019.10.14.10.06.24; Mon, 14 Oct 2019 10:06:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=UTqEumcJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387877AbfJNQlO (ORCPT + 99 others); Mon, 14 Oct 2019 12:41:14 -0400 Received: from mail-pl1-f195.google.com ([209.85.214.195]:39715 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727038AbfJNQlO (ORCPT ); Mon, 14 Oct 2019 12:41:14 -0400 Received: by mail-pl1-f195.google.com with SMTP id s17so8245374plp.6 for ; Mon, 14 Oct 2019 09:41:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=yGcjVdTMGCzNncU46yGhvMqxXtCQHqNYV1cWFlBhCFE=; b=UTqEumcJsYD/xtVqbGC9RIRyR9f5F7HVeG27AzE/kHX7uxepU/UGPH1Iu+JVIWcsei 4M2VZGEmn0hHVoY+oy6AmYFrzZ6dl2qMeOe+hQR3mTShX2yHKbl0Xkpz0pxpr5YIZbtc mQz8RiLjsH2xQiWN9ruFSYFM8X8Mf8ocSN/XQEPxZU4Rn5ehyLIHJeoMnjIAX5OBZfAe sWJvJ/2XoujpgHXAEnX3o0DyiBq0FNMCuCS2i9vb31T68NwVpCUrZ4E4KSkHJhPGz1En bSuffD4986jCMaIRgfQhiXgVN/uBCfAs1FuA1dUhwuOXzke2xJ5SlitPeuy74f0Ke867 epdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=yGcjVdTMGCzNncU46yGhvMqxXtCQHqNYV1cWFlBhCFE=; b=Pys2qSGiFHgBeuZyQSZwv5n6ST2J6kg171ij5LhKZR5y7jsBhYmqYKie80eyKon6Ze ipEIqseijRRKVuuVBvUafxcuM75V3ZKiLg7gKXwPaPQFvtxF5wIZILnKTm2Q/gr484tn yfVd/VyROWg4POtbxwXsw9c+WtEciRkXKRSzoyMxv5aZM3K6FysNRGE2NDuwbv2bj0SA MGWzakHRjQ17s9U6OdDLR5lT96Vh2/4zg3Wwi9+fGnYzwn/JVSzypNwGW4Ac+prKQigs 3u7QiJYXn70lgIwMST4O+6H2HThL3C3dN68PTH6v9fvtayKkxs+zBfXS4gHznuNW0dFP whuw== X-Gm-Message-State: APjAAAWCiJchpcsfBEa2aqlPTCAnM3FP9ItIw0QdVFmMWkss0+zIFnUr cTMM0sKjC0vh869l1446H8Glduvw X-Received: by 2002:a17:902:222:: with SMTP id 31mr31672319plc.169.1571071273533; Mon, 14 Oct 2019 09:41:13 -0700 (PDT) Received: from google.com ([2620:15c:211:1:3e01:2939:5992:52da]) by smtp.gmail.com with ESMTPSA id m22sm18841635pgj.29.2019.10.14.09.41.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 14 Oct 2019 09:41:12 -0700 (PDT) Date: Mon, 14 Oct 2019 09:41:10 -0700 From: Minchan Kim To: Vitaly Wool Cc: Linux-MM , Andrew Morton , Dan Streetman , Sergey Senozhatsky , LKML , Vlastimil Babka , Shakeel Butt , Henry Burns , Theodore Ts'o Subject: Re: [PATCH 0/3] Allow ZRAM to use any zpool-compatible backend Message-ID: <20191014164110.GA58307@google.com> References: <20191010230414.647c29f34665ca26103879c4@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191010230414.647c29f34665ca26103879c4@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 10, 2019 at 11:04:14PM +0300, Vitaly Wool wrote: > The coming patchset is a new take on the old issue: ZRAM can currently be used only with zsmalloc even though this may not be the optimal combination for some configurations. The previous (unsuccessful) attempt dates back to 2015 [1] and is notable for the heated discussions it has caused. > > The patchset in [1] had basically the only goal of enabling ZRAM/zbud combo which had a very narrow use case. Things have changed substantially since then, and now, with z3fold used widely as a zswap backend, I, as the z3fold maintainer, am getting requests to re-interate on making it possible to use ZRAM with any zpool-compatible backend, first of all z3fold. > > The preliminary results for this work have been delivered at Linux Plumbers this year [2]. The talk at LPC, though having attracted limited interest, ended in a consensus to continue the work and pursue the goal of decoupling ZRAM from zsmalloc. > > The current patchset has been stress tested on arm64 and x86_64 devices, including the Dell laptop I'm writing this message on now, not to mention several QEmu confugirations. > > [1] https://lkml.org/lkml/2015/9/14/356 > [2] https://linuxplumbersconf.org/event/4/contributions/551/ Please describe what's the usecase in real world, what's the benefit zsmalloc cannot fulfill by desgin and how it's significant. I really don't want to make fragmentaion of allocator so we should really see how zsmalloc cannot achieve things if you are claiming. Please tell us how to test it so that we could investigate what's the root cause.