All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Shuoran Liu <liushuoran@huawei.com>,
	jaegeuk@kernel.org, chao2.yu@samsung.com
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: retrieve IO write stat from the right place
Date: Tue, 29 Mar 2016 21:29:40 +0800	[thread overview]
Message-ID: <56FA8344.4090500@kernel.org> (raw)
In-Reply-To: <1459245615-21023-1-git-send-email-liushuoran@huawei.com>

On 2016/3/29 18:00, Shuoran Liu wrote:
> In the following patch,
> 
>     f2fs: split journal cache from curseg cache
> 
> journal cache is split from curseg cache. So IO write statistics should be
> retrived from journal cache but not curseg->sum_blk. Otherwise, it will
> get 0, and the stat is lost.

My bad, thanks for catching this.

Reviewed-by: Chao Yu <chao@kernel.org>

> 
> Signed-off-by: Shuoran Liu <liushuoran@huawei.com>
> ---
>  fs/f2fs/super.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index 15bb81f..e2787c8 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -1442,7 +1442,7 @@ try_onemore:
>  	seg_i = CURSEG_I(sbi, CURSEG_HOT_NODE);
>  	if (__exist_node_summaries(sbi))
>  		sbi->kbytes_written =
> -			le64_to_cpu(seg_i->sum_blk->journal.info.kbytes_written);
> +			le64_to_cpu(seg_i->journal->info.kbytes_written);
>  
>  	build_gc_manager(sbi);
>  
> 

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140

      reply	other threads:[~2016-03-29 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 10:00 [PATCH] f2fs: retrieve IO write stat from the right place Shuoran Liu
2016-03-29 13:29 ` Chao Yu [this message]

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=56FA8344.4090500@kernel.org \
    --to=chao@kernel.org \
    --cc=chao2.yu@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=liushuoran@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: link
Be 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.