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=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_MUTT 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 C9E67C31E51 for ; Tue, 18 Jun 2019 07:05:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A4AF62080C for ; Tue, 18 Jun 2019 07:05:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560841509; bh=sFiwjoiPTET5brttrBZ5SN7nqR5IKnSGCmTkDzWrNsE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Up8csNsS1CBjnKDfP3SVblAGhd/n1ZT3PE+PmPV086ARiOgxbYm31ehg9g0xztEgF Nix94lHk4rPmUq5bsyw4mKTKBH+QF4u8RP7Z2AM+gqQ03Tn3umzkViCRZZbzqOBSV1 AB+sb6qDvMn8aedCmisXaocs+VniUlV5vhaA69xY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728987AbfFRHFI (ORCPT ); Tue, 18 Jun 2019 03:05:08 -0400 Received: from mail.kernel.org ([198.145.29.99]:34734 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726023AbfFRHFG (ORCPT ); Tue, 18 Jun 2019 03:05:06 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 65BAF20665; Tue, 18 Jun 2019 07:05:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560841505; bh=sFiwjoiPTET5brttrBZ5SN7nqR5IKnSGCmTkDzWrNsE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=M5uVEr2zVBCbGBHG19hY6OK3+CLOHa/IdTmxqN6g+8XJ8jtRuyDJBDlKL6jwJc3aP k2uKsD31+yqCJJDO4TIGrWIY7RhzHYW40hn7j9uOWfsztWsQOKiDfhQuElg6YLgfah MFj6cslduTCzrjIz4h15pa5nFFVSJuWSYC4SdzoI= Date: Tue, 18 Jun 2019 09:05:03 +0200 From: Greg Kroah-Hartman To: Gao Xiang Cc: devel@driverdev.osuosl.org, linux-erofs@lists.ozlabs.org, chao@kernel.org, LKML , weidu.du@huawei.com, Fang Wei , linux-fsdevel@vger.kernel.org, Miao Xie Subject: Re: [RFC PATCH 0/8] staging: erofs: decompression inplace approach Message-ID: <20190618070503.GB9160@kroah.com> References: <20190614181619.64905-1-gaoxiang25@huawei.com> <20190617203609.GA22034@kroah.com> <20190618054709.GA4271@kroah.com> <20190618064523.GA6015@kroah.com> <2a6abbf9-20a9-c1dd-0091-d8e3009037eb@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a6abbf9-20a9-c1dd-0091-d8e3009037eb@huawei.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 18, 2019 at 02:52:21PM +0800, Gao Xiang wrote: > > > On 2019/6/18 14:45, Greg Kroah-Hartman wrote: > > On Tue, Jun 18, 2019 at 02:18:00PM +0800, Gao Xiang wrote: > >> > >> > >> On 2019/6/18 13:47, Greg Kroah-Hartman wrote: > >>> On Tue, Jun 18, 2019 at 09:47:08AM +0800, Gao Xiang wrote: > >>>> > >>>> > >>>> On 2019/6/18 4:36, Greg Kroah-Hartman wrote: > >>>>> On Sat, Jun 15, 2019 at 02:16:11AM +0800, Gao Xiang wrote: > >>>>>> At last, this is RFC patch v1, which means it is not suitable for > >>>>>> merging soon... I'm still working on it, testing its stability > >>>>>> these days and hope these patches get merged for 5.3 LTS > >>>>>> (if 5.3 is a LTS version). > >>>>> > >>>>> Why would 5.3 be a LTS kernel? > >>>>> > >>>>> curious as to how you came up with that :) > >>>> > >>>> My personal thought is about one LTS kernel one year... > >>>> Usually 5 versions after the previous kernel...(4.4 -> 4.9 -> 4.14 -> 4.19), > >>>> which is not suitable for all historical LTSs...just prepare for 5.3... > >>> > >>> I try to pick the "last" kernel that is released each year, which > >>> sometimes is 5 kernels, sometimes 4, sometimes 6, depending on the > >>> release cycle. > >>> > >>> So odds are it will be 5.4 for the next LTS kernel, but we will not know > >>> more until it gets closer to release time. > >> > >> Thanks for kindly explanation :) > >> > >> Anyway, I will test these patches, land to our commerical products and try the best > >> efforts on making it more stable for Linux upstream to merge. > > > > Sounds great. > > > > But why do you need to add compression to get this code out of staging? > > Why not move it out now and then add compression and other new features > > to it then? > > Move out of staging could be over several linux versions since I'd like to get > majority fs people agreed to this. You never know until you try :) > Decompression inplace is an important part of erofs to show its performance > benefits over existed compress filesystems and I tend to merge it in advance. There is no requirement to show benefits over other filesystems in order to get it merged, but I understand the feeling. That's fine, we can wait, we are not going anywhere... thanks, greg k-h