From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CBF13C4CECE for ; Mon, 14 Oct 2019 10:36:01 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 8B48420663 for ; Mon, 14 Oct 2019 10:36:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="hKE/qWvV" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8B48420663 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 538AE8E0006; Mon, 14 Oct 2019 06:36:00 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 4E8D98E0001; Mon, 14 Oct 2019 06:36:00 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3FE658E0006; Mon, 14 Oct 2019 06:36:00 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0056.hostedemail.com [216.40.44.56]) by kanga.kvack.org (Postfix) with ESMTP id 1F7438E0001 for ; Mon, 14 Oct 2019 06:36:00 -0400 (EDT) Received: from smtpin11.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with SMTP id AC545181AEF15 for ; Mon, 14 Oct 2019 10:35:59 +0000 (UTC) X-FDA: 76042034838.11.anger82_34425d3603440 X-HE-Tag: anger82_34425d3603440 X-Filterd-Recvd-Size: 4755 Received: from mail-pl1-f195.google.com (mail-pl1-f195.google.com [209.85.214.195]) by imf50.hostedemail.com (Postfix) with ESMTP for ; Mon, 14 Oct 2019 10:35:58 +0000 (UTC) Received: by mail-pl1-f195.google.com with SMTP id j11so7836333plk.3 for ; Mon, 14 Oct 2019 03:35:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=RBxhSOhGoBq865LLyCQ9HRQenV+KPGNi6KV33B0fJwk=; b=hKE/qWvVJ+nBCGXp08FZ1EhL0d/2DPj/AgqTRDupb+P51bWIiyZU/69pZfcptrERTc vScq0gMH/PVrKAIJsdH9B69bFNH0j5EWNQk+hKVy3H6ipxIyv0yKReMhi8a2H/OJOX5D cyHXukI+kjUhp0cAgZEnT39S06eg/3ZQS5WzNW+TNa6u3avSgTUUkbAl930dxBp4Bl0i QKxaKJg4QKHqK4KsN2cmo1wXYDZT4uthupXa0werf9bJCleNMbKPQ+zlWGNUIEYghwxm anxreqA+qVO5s7VXERhGj6XiFspq7IIso5zKAGb/9FrSacDrLjA6zr8lZUiC0b725X1Z e0dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=RBxhSOhGoBq865LLyCQ9HRQenV+KPGNi6KV33B0fJwk=; b=lw3V67P4n1p7qDAo3moyBpwVkd+PADQ9jNx9zK8KejNbQlIHPH0lnuTKib7q0nqg9X PHgSjNX998yyt8oMtdpUknLtsSGxg448cren0X6LaqTO5zV/z3mcDuOBWMRweTP/Y6we wmAtUcupmoVcWKnjMozVThTivgyzlWDn+/gzk/WXpumLiOG4fjkle4S1opKVOY+1gmrc EjCxuUSiLj2VbiNvXpIrlSmAqkUpK/L7COPRCVIz6cXScJoh6v02BIcy4TOlJa2BvW7T CCd5pl7vNhrBRVpPclCFEFXaVBNPRU3TdJS3UeXCSRVD8uJIu1/TYMr1DIeqi8OanXBO Bu6g== X-Gm-Message-State: APjAAAVbBWY8KbHSoR/+Io7sj0UEJDZ+KDfzF6y2ZaKP2IVG8UmSPZzE w4EoXL6ubPecBxaI1uWclFo= X-Google-Smtp-Source: APXvYqxwFQ5rWEaHyO1+CQZGJqSJ7RaE3hT+S5ikE/d9iGfP2L08synqCGkRUuyXAhI2gMzWb5KLKA== X-Received: by 2002:a17:902:9a06:: with SMTP id v6mr29484930plp.221.1571049357916; Mon, 14 Oct 2019 03:35:57 -0700 (PDT) Received: from localhost ([211.246.68.186]) by smtp.gmail.com with ESMTPSA id k95sm17287237pje.10.2019.10.14.03.35.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 14 Oct 2019 03:35:57 -0700 (PDT) Date: Mon, 14 Oct 2019 19:33:41 +0900 From: Sergey Senozhatsky To: Vitaly Wool Cc: Linux-MM , Andrew Morton , Dan Streetman , Minchan Kim , 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: <20191014103341.GA36860@jagdpanzerIV> 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.12.2 (2019-09-21) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000262, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hi, On (10/10/19 23:04), 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. Oh, right, I do recall it. > 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. A quick question, what are the technical reasons to prefer allocator X over zsmalloc? Some data would help, I guess. > 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. [..] > [1] https://lkml.org/lkml/2015/9/14/356 I need to re-read it, thanks for the link. IIRC, but maybe I'm wrong, one of the things Minchan was not happy with was increased maintenance cost. So, perhaps, this also should be discuss/addressed (and maybe even in the first place). -ss