linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>, <chao@kernel.org>
Subject: Re: [PATCH v4] f2fs: compress: add compress_inode to cache compressed blockst
Date: Thu, 4 Feb 2021 11:25:25 +0800	[thread overview]
Message-ID: <46e9924c-0086-cd2a-2e93-7149b92ba27e@huawei.com> (raw)
In-Reply-To: <20210202080056.51658-1-yuchao0@huawei.com>

Jaegeuk,

On 2021/2/2 16:00, Chao Yu wrote:
> -	for (i = 0; i < dic->nr_cpages; i++) {
> +	for (i = 0; i < cc->nr_cpages; i++) {
>   		struct page *page = dic->cpages[i];

por_fsstress still hang in this line?

Thanks,

>   		block_t blkaddr;
>   		struct bio_post_read_ctx *ctx;
> @@ -2201,6 +2207,14 @@ int f2fs_read_multi_pages(struct compress_ctx *cc, struct bio **bio_ret,
>   		blkaddr = data_blkaddr(dn.inode, dn.node_page,
>   						dn.ofs_in_node + i + 1);
>   
> +		f2fs_wait_on_block_writeback(inode, blkaddr);
> +
> +		if (f2fs_load_compressed_page(sbi, page, blkaddr)) {
> +			if (atomic_dec_and_test(&dic->remaining_pages))
> +				f2fs_decompress_cluster(dic);
> +			continue;
> +		}
> +

  reply	other threads:[~2021-02-04  3:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  8:00 [PATCH v4] f2fs: compress: add compress_inode to cache compressed blockst Chao Yu
2021-02-04  3:25 ` Chao Yu [this message]
2021-02-28  5:09   ` Jaegeuk Kim
2021-03-04 20:20     ` [f2fs-dev] " Jaegeuk Kim
2021-03-05  3:07       ` Chao Yu
2021-03-09  0:01         ` Jaegeuk Kim
2021-03-09  2:49           ` Chao Yu
2021-03-10 20:52             ` Jaegeuk Kim
2021-04-21  9:08               ` Chao Yu
2021-04-22  3:59                 ` Jaegeuk Kim
2021-04-22  6:07                   ` Chao Yu
2021-05-10  9:05                     ` Chao Yu
2021-05-10 14:35                       ` Jaegeuk Kim

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=46e9924c-0086-cd2a-2e93-7149b92ba27e@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).