From: Haicheng Li <haicheng.li@linux.intel.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-kernel@vger.kernel.org,
Haicheng Li <haicheng.lee@gmail.com>,
linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/4] f2fs: optimize scan_nat_page()
Date: Wed, 8 May 2013 13:31:34 +0800 [thread overview]
Message-ID: <20130508053134.GA8705@hli22-desktop> (raw)
In-Reply-To: <1367922988.16581.45.camel@kjgkr>
On Tue, May 07, 2013 at 07:36:28PM +0900, Jaegeuk Kim wrote:
> Hi,
>
> 2013-05-06 (월), 23:15 +0800, Haicheng Li:
> > if (nm_i->fcnt > 2 * MAX_FREE_NIDS)
> > - return 0;
> > + return -1;
>
> We should check all the handler of add_free_nid().
yes, sorry that I missed double checking it while rebasing this patch
from master to dev branch, since there is only one handler on the master branch.
> So, plz see the below modified patch.
> > + if (blk_addr == NULL_ADDR) {
> > + cnt = add_free_nid(nm_i, start_nid);
> > + if (cnt < 0)
> > + break;
> > + }
>
> Here we need to eliminate cnt.
sure, harmless & can reduce the code line.
and the below patch looks good to me. Thanks.
> -----
> From e2da02f0ba045f792d166ac8215d04474c06f319 Mon Sep 17 00:00:00 2001
> From: Haicheng Li <haicheng.li@linux.intel.com>
> Date: Mon, 6 May 2013 23:15:43 +0800
> Subject: [PATCH] f2fs: optimize scan_nat_page()
> Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
> linux-f2fs-devel@lists.sourceforge.net
>
> When nm_i->fcnt > 2 * MAX_FREE_NIDS, stop scanning other NAT entries.
>
> Signed-off-by: Haicheng Li <haicheng.li@linux.intel.com>
> [Jaegeuk Kim: fix handling the return value of add_free_nid()]
> Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
> ---
> fs/f2fs/node.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> index 122200e..e42934e 100644
> --- a/fs/f2fs/node.c
> +++ b/fs/f2fs/node.c
> @@ -1254,7 +1254,7 @@ static int add_free_nid(struct f2fs_nm_info *nm_i,
> nid_t nid)
> struct free_nid *i;
>
> if (nm_i->fcnt > 2 * MAX_FREE_NIDS)
> - return 0;
> + return -1;
>
> /* 0 nid should not be used */
> if (nid == 0)
> @@ -1302,12 +1302,16 @@ static void scan_nat_page(struct f2fs_nm_info
> *nm_i,
> i = start_nid % NAT_ENTRY_PER_BLOCK;
>
> for (; i < NAT_ENTRY_PER_BLOCK; i++, start_nid++) {
> +
> if (start_nid >= nm_i->max_nid)
> break;
> - blk_addr = le32_to_cpu(nat_blk->entries[i].block_addr);
> +
> + blk_addr = le32_to_cpu(nat_blk->entries[i].block_addr);
> BUG_ON(blk_addr == NEW_ADDR);
> - if (blk_addr == NULL_ADDR)
> - add_free_nid(nm_i, start_nid);
> + if (blk_addr == NULL_ADDR) {
> + if (add_free_nid(nm_i, start_nid) < 0)
> + break;
> + }
> }
> }
>
> @@ -1655,7 +1659,7 @@ flush_now:
> }
>
> if (nat_get_blkaddr(ne) == NULL_ADDR &&
> - !add_free_nid(NM_I(sbi), nid)) {
> + add_free_nid(NM_I(sbi), nid) <= 0) {
> write_lock(&nm_i->nat_tree_lock);
> __del_from_nat_cache(nm_i, ne);
> write_unlock(&nm_i->nat_tree_lock);
> --
> 1.8.1.3.566.gaa39828
>
next prev parent reply other threads:[~2013-05-08 5:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 15:15 [PATCH V2 0/4] f2fs: various optimization & bugfixing for node management Haicheng Li
2013-05-06 15:15 ` [PATCH 1/4] f2fs: bugfix for alloc_nid_failed() Haicheng Li
2013-05-06 15:15 ` [PATCH 2/4] f2fs: code cleanup for scan_nat_page() and build_free_nids() Haicheng Li
2013-05-06 15:15 ` [PATCH 3/4] f2fs: optimize scan_nat_page() Haicheng Li
2013-05-07 10:36 ` Jaegeuk Kim
2013-05-08 5:31 ` Haicheng Li [this message]
2013-05-06 15:15 ` [PATCH 4/4] f2fs: optimize build_free_nids() Haicheng Li
2013-05-07 10:33 ` Jaegeuk Kim
2013-05-08 6:24 ` Haicheng Li
2013-05-08 9:50 ` Jaegeuk Kim
2013-05-08 11:50 ` Haicheng Li
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=20130508053134.GA8705@hli22-desktop \
--to=haicheng.li@linux.intel.com \
--cc=haicheng.lee@gmail.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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).