From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Yue Hu <zbestahu@gmail.com>
Cc: xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org,
jefflexu@linux.alibaba.com, linux-kernel@vger.kernel.org,
huyue2@coolpad.com, zhangwen@coolpad.com
Subject: Re: [PATCH] erofs: remove unneeded icur field from struct z_erofs_decompress_frontend
Date: Mon, 17 Apr 2023 15:12:31 +0800 [thread overview]
Message-ID: <a8b9a758-d469-b9a6-f5e8-8f3768e2ea81@linux.alibaba.com> (raw)
In-Reply-To: <20230417151506.00006565.zbestahu@gmail.com>
On 2023/4/17 15:15, Yue Hu wrote:
> On Mon, 17 Apr 2023 15:00:25 +0800
> Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
>
..
>>
>> Although please help refine the comment below:
>>
>> /* scan & fill inplace I/O pages in the reverse order */
>
> Ok, will refine it in v2.
I rethink this, I don't want to go far in this way, and this makes a
O(n) scan into O(n^2) when a single inplace I/O page is added.
So sorry, I don't think it's a good way, although I also don't think
`icur` is a good name and we might need to find a better name.
Thanks,
Gao Xiang
>
>>
>> Thanks,
>> Gao Xiang
>>
>>>> + unsigned int icur = pcl->pclusterpages;
>>>> - while (fe->icur > 0) {
>>>> - if (!cmpxchg(&pcl->compressed_bvecs[--fe->icur].page,
>>>> + while (icur > 0) {
>>>> + if (!cmpxchg(&pcl->compressed_bvecs[--icur].page,
>>>> NULL, bvec->page)) {
>>>> - pcl->compressed_bvecs[fe->icur] = *bvec;
>>>> + pcl->compressed_bvecs[icur] = *bvec;
>>>> return true;
>>>> }
>>>> }
>>>> @@ -877,8 +876,6 @@ static int z_erofs_collector_begin(struct z_erofs_decompress_frontend *fe)
>>>> }
>>>> z_erofs_bvec_iter_begin(&fe->biter, &fe->pcl->bvset,
>>>> Z_EROFS_INLINE_BVECS, fe->pcl->vcnt);
>>>> - /* since file-backed online pages are traversed in reverse order */
>>>> - fe->icur = z_erofs_pclusterpages(fe->pcl);
>>>> return 0;
>>>> }
next prev parent reply other threads:[~2023-04-17 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 6:41 Yue Hu
2023-04-17 6:52 ` Gao Xiang
2023-04-17 7:00 ` Gao Xiang
2023-04-17 7:15 ` Yue Hu
2023-04-17 7:12 ` Gao Xiang [this message]
2023-04-17 7:44 ` Yue Hu
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=a8b9a758-d469-b9a6-f5e8-8f3768e2ea81@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.com \
--cc=zhangwen@coolpad.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®