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=-13.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=ham 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 712C1C4338F for ; Tue, 17 Aug 2021 14:38:40 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 09D9760F39 for ; Tue, 17 Aug 2021 14:38:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 09D9760F39 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4Gptv252nBz30Hv for ; Wed, 18 Aug 2021 00:38:38 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=linux.alibaba.com (client-ip=115.124.30.44; helo=out30-44.freemail.mail.aliyun.com; envelope-from=hsiangkao@linux.alibaba.com; receiver=) Received: from out30-44.freemail.mail.aliyun.com (out30-44.freemail.mail.aliyun.com [115.124.30.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4Gptts4yrXz30CX for ; Wed, 18 Aug 2021 00:38:25 +1000 (AEST) X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R291e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e01e04400; MF=hsiangkao@linux.alibaba.com; NM=1; PH=DS; RN=5; SR=0; TI=SMTPD_---0UjSfEIs_1629211085; Received: from B-P7TQMD6M-0146.local(mailfrom:hsiangkao@linux.alibaba.com fp:SMTPD_---0UjSfEIs_1629211085) by smtp.aliyun-inc.com(127.0.0.1); Tue, 17 Aug 2021 22:38:06 +0800 Date: Tue, 17 Aug 2021 22:38:04 +0800 From: Gao Xiang To: Yue Hu Subject: Re: [PATCH] erofs-utils: add clusterofs zero check to write_uncompressed_extent() Message-ID: References: <20210817040605.732-1-zbestahu@gmail.com> <20210817221046.000037aa.zbestahu@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210817221046.000037aa.zbestahu@gmail.com> X-BeenThere: linux-erofs@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development of Linux EROFS file system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: xiang@kernel.org, linux-erofs@lists.ozlabs.org, huyue2@yulong.com, zbestahu@163.com Errors-To: linux-erofs-bounces+linux-erofs=archiver.kernel.org@lists.ozlabs.org Sender: "Linux-erofs" On Tue, Aug 17, 2021 at 10:10:46PM +0800, Yue Hu wrote: > Hi Xiang, > > On Tue, 17 Aug 2021 21:13:14 +0800 > Gao Xiang wrote: > > > Hi Yue, > > > > On Tue, Aug 17, 2021 at 12:06:04PM +0800, Yue Hu wrote: > > > From: Yue Hu > > > > > > No need to reset clusterofs to 0 if it's already 0. Acturally, we also > > > observed that case frequently. Let's avoid it. > > > > > > Signed-off-by: Yue Hu > > > --- > > > lib/compress.c | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/lib/compress.c b/lib/compress.c > > > index 40723a1..a8ebbc1 100644 > > > --- a/lib/compress.c > > > +++ b/lib/compress.c > > > @@ -130,7 +130,7 @@ static int write_uncompressed_extent(struct z_erofs_vle_compress_ctx *ctx, > > > unsigned int count; > > > > > > /* reset clusterofs to 0 if permitted */ > > > - if (!erofs_sb_has_lz4_0padding() && > > > + if (!erofs_sb_has_lz4_0padding() && ctx->clusterofs && > > > > Also out of curiosity, which means erofs is used without lz4 0padding? > > Yes. We are using legacy compression layout now. Ok, I think sometime I will seperate it into (non)compact compress indexes, and (non)0padding. It was once named as legacy just before Linux < 5.3 didn't support them. By default, the preferred option now I think is compact and 0padding. 0padding will enable in-place decompression (and LZMA will always enable it.) compact will reduce metadata even further as long as the compressed data is consecutive (e.g. 2 bytes each lcluster for compact indexes rather than 8 bytes each lcluster for noncompact indexes, but anyway, either (non)compact metadata can support effective data random access.) Ok, if it's somewhat kernel 4.19 based code, I'd suggest to upgrade the codebase at least to 5.4, not because 4.19 doesn't work, but really for some performance concern.... Thanks, Gao Xiang