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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 47AB6C433F5 for ; Wed, 13 Oct 2021 11:58: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 B724F610E5 for ; Wed, 13 Oct 2021 11:58:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org B724F610E5 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 4HTrf61xS3z2ypR for ; Wed, 13 Oct 2021 22:58:38 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=linux.alibaba.com (client-ip=115.124.30.43; helo=out30-43.freemail.mail.aliyun.com; envelope-from=hsiangkao@linux.alibaba.com; receiver=) Received: from out30-43.freemail.mail.aliyun.com (out30-43.freemail.mail.aliyun.com [115.124.30.43]) (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 4HTrf23x9hz2yWn for ; Wed, 13 Oct 2021 22:58:33 +1100 (AEDT) X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R141e4; 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=8; SR=0; TI=SMTPD_---0UrhChj4_1634126307; Received: from B-P7TQMD6M-0146.local(mailfrom:hsiangkao@linux.alibaba.com fp:SMTPD_---0UrhChj4_1634126307) by smtp.aliyun-inc.com(127.0.0.1); Wed, 13 Oct 2021 19:58:28 +0800 Date: Wed, 13 Oct 2021 19:58:26 +0800 From: Gao Xiang To: Yue Hu Subject: Re: [PATCH] erofs: fix the per-CPU buffer decompression for small output size Message-ID: References: <20211013092906.1434-1-zbestahu@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: 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: linux-kernel@vger.kernel.org, zbestahu@163.com, huyue2@yulong.com, linux-erofs@lists.ozlabs.org, zhangwen@yulong.com Errors-To: linux-erofs-bounces+linux-erofs=archiver.kernel.org@lists.ozlabs.org Sender: "Linux-erofs" On Wed, Oct 13, 2021 at 07:51:55PM +0800, Gao Xiang wrote: > Hi Yue, > > On Wed, Oct 13, 2021 at 05:29:05PM +0800, Yue Hu wrote: > > From: Yue Hu > > > > Note that z_erofs_lz4_decompress() will return a positive value if > > decompression succeeds. However, we do not copy_from_pcpubuf() due > > to !ret. Let's fix it. > > > > Signed-off-by: Yue Hu > > Thanks for catching this. This is a valid issue, but it has no real > impact to the current kernels since such pcluster in practice will be > !inplace_io and trigger "if (nrpages_out == 1 && !rq->inplace_io) {" > above for upstream strategies. > > Our customized lz4 implementation will return 0 if success instead, so > it has no issue to our previous products as well. > > For such cases, how about updating z_erofs_lz4_decompress() to return > 0 if success instead rather than outputsize. Since I'll return 0 if > success for LZMA as well. In addition, I'm fine to getting rid of such path as well, since it has no real impact to our current upstream decompression strategy. If it has some use cases due to decompression strategy change, we could re-add it with some evaluation (some real numbers) later. Thanks, Gao Xiang > > Thanks, > Gao Xiang