From: Chao Yu <chao2.yu@samsung.com>
To: "'Wanpeng Li'" <wanpeng.li@linux.intel.com>,
"'Jaegeuk Kim'" <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH 2/2] f2fs: fix the number of orphan inode blocks
Date: Thu, 26 Feb 2015 09:33:55 +0800 [thread overview]
Message-ID: <013201d05164$637b7880$2a726980$@samsung.com> (raw)
In-Reply-To: <1424908641-76409-2-git-send-email-wanpeng.li@linux.intel.com>
Hi Wanpeng,
> -----Original Message-----
> From: Wanpeng Li [mailto:wanpeng.li@linux.intel.com]
> Sent: Thursday, February 26, 2015 7:57 AM
> To: Jaegeuk Kim
> Cc: Wanpeng Li; linux-kernel@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH 2/2] f2fs: fix the number of orphan inode blocks
>
> cp_pack_start_sum is calculated in do_checkpoint and is equal to
> cpu_to_le32(1 + cp_payload_blks + orphan_blocks). The number of
> orphan inode blocks is take advantage of by recover_orphan_inodes
> to readahead meta pages and recovery inodes. However, current codes
> forget to reduce the number of cp payload blocks when calculate
> the number of orphan inode blocks. This patch fix it.
Nice work! looks good to me. :)
>
> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
next prev parent reply other threads:[~2015-02-26 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 23:57 [PATCH 1/2] f2fs: introduce macro __cp_payload Wanpeng Li
2015-02-25 23:57 ` [PATCH 2/2] f2fs: fix the number of orphan inode blocks Wanpeng Li
2015-02-26 1:33 ` Chao Yu [this message]
2015-02-27 9:11 ` [f2fs-dev] " Wanpeng Li
2015-02-26 1:27 ` [f2fs-dev] [PATCH 1/2] f2fs: introduce macro __cp_payload Chao Yu
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='013201d05164$637b7880$2a726980$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wanpeng.li@linux.intel.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