From: Gao Xiang <gaoxiang25@huawei.com> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: <devel@driverdev.osuosl.org>, Miao Xie <miaoxie@huawei.com>, <chao@kernel.org>, LKML <linux-kernel@vger.kernel.org>, <weidu.du@huawei.com>, Fang Wei <fangwei1@huawei.com>, <linux-fsdevel@vger.kernel.org>, <linux-erofs@lists.ozlabs.org> Subject: Re: [RFC PATCH 0/8] staging: erofs: decompression inplace approach Date: Tue, 18 Jun 2019 14:18:00 +0800 [thread overview] Message-ID: <df18d7f9-f65a-5697-c7c4-edb1ad846c3e@huawei.com> (raw) In-Reply-To: <20190618054709.GA4271@kroah.com> 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. Thanks, Gao Xiang > > thanks, > > greg k-h >
WARNING: multiple messages have this Message-ID (diff)
From: gaoxiang25@huawei.com (Gao Xiang) Subject: [RFC PATCH 0/8] staging: erofs: decompression inplace approach Date: Tue, 18 Jun 2019 14:18:00 +0800 [thread overview] Message-ID: <df18d7f9-f65a-5697-c7c4-edb1ad846c3e@huawei.com> (raw) In-Reply-To: <20190618054709.GA4271@kroah.com> On 2019/6/18 13:47, Greg Kroah-Hartman wrote: > On Tue, Jun 18, 2019@09:47:08AM +0800, Gao Xiang wrote: >> >> >> On 2019/6/18 4:36, Greg Kroah-Hartman wrote: >>> On Sat, Jun 15, 2019@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. Thanks, Gao Xiang > > thanks, > > greg k-h >
next prev parent reply other threads:[~2019-06-18 7:03 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-14 18:16 [RFC PATCH 0/8] staging: erofs: decompression inplace approach Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-14 18:16 ` [RFC PATCH 1/8] staging: erofs: add compacted ondisk compression indexes Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-14 18:16 ` [RFC PATCH 2/8] staging: erofs: add compacted compression indexes support Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-14 18:16 ` [RFC PATCH 3/8] staging: erofs: move per-CPU buffers implementation to utils.c Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-14 18:16 ` [RFC PATCH 4/8] staging: erofs: move stagingpage operations to compress.h Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-14 18:16 ` [RFC PATCH 5/8] staging: erofs: introduce generic decompression backend Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-14 18:16 ` [RFC PATCH 6/8] staging: erofs: introduce LZ4 decompression inplace Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-14 18:16 ` [RFC PATCH 7/8] staging: erofs: switch to new decompression backend Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-14 18:16 ` [RFC PATCH 8/8] staging: erofs: integrate decompression inplace Gao Xiang 2019-06-14 18:16 ` Gao Xiang 2019-06-17 20:36 ` [RFC PATCH 0/8] staging: erofs: decompression inplace approach Greg Kroah-Hartman 2019-06-17 20:36 ` Greg Kroah-Hartman 2019-06-18 1:47 ` Gao Xiang 2019-06-18 1:47 ` Gao Xiang 2019-06-18 5:47 ` Greg Kroah-Hartman 2019-06-18 5:47 ` Greg Kroah-Hartman 2019-06-18 6:18 ` Gao Xiang [this message] 2019-06-18 6:18 ` Gao Xiang 2019-06-18 6:45 ` Greg Kroah-Hartman 2019-06-18 6:45 ` Greg Kroah-Hartman 2019-06-18 6:52 ` Gao Xiang 2019-06-18 6:52 ` Gao Xiang 2019-06-18 7:05 ` Greg Kroah-Hartman 2019-06-18 7:05 ` Greg Kroah-Hartman 2019-06-18 7:13 ` Gao Xiang 2019-06-18 7:13 ` Gao Xiang
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=df18d7f9-f65a-5697-c7c4-edb1ad846c3e@huawei.com \ --to=gaoxiang25@huawei.com \ --cc=chao@kernel.org \ --cc=devel@driverdev.osuosl.org \ --cc=fangwei1@huawei.com \ --cc=gregkh@linuxfoundation.org \ --cc=linux-erofs@lists.ozlabs.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=miaoxie@huawei.com \ --cc=weidu.du@huawei.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.