From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Chao Yu <chao2.yu@samsung.com>
Cc: "'Kim'" <jaegeuk.kim@samsung.com>,
"'linux-kernel'" <linux-kernel@vger.kernel.org>,
"'f2fs'" <linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 1/5] f2fs: update start nid only once each circle
Date: Mon, 10 Mar 2014 09:32:12 +0800 [thread overview]
Message-ID: <531D161C.8080001@cn.fujitsu.com> (raw)
In-Reply-To: <001301cf3ac4$3220b8c0$96622a40$@samsung.com>
On 03/08/2014 07:46 PM, Chao Yu wrote:
> Hi Gu,
>
>> -----Original Message-----
>> From: Gu Zheng [mailto:guz.fnst@cn.fujitsu.com]
>> Sent: Friday, March 07, 2014 6:43 PM
>> To: Kim
>> Cc: linux-kernel; f2fs
>> Subject: [f2fs-dev] [PATCH 1/5] f2fs: update start nid only once each circle
>>
>>
>> Signed-off-by: Gu Zheng <guz.fnst@cn.fujitsu.com>
>
> Reviewed-by: Chao Yu <chao2.yu@samsung.com>
>
>> ---
>> fs/f2fs/node.c | 6 +++++-
>> 1 files changed, 5 insertions(+), 1 deletions(-)
>>
>> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
>> index 8c14110..9653096 100644
>> --- a/fs/f2fs/node.c
>> +++ b/fs/f2fs/node.c
>> @@ -1875,11 +1875,15 @@ void destroy_node_manager(struct f2fs_sb_info *sbi)
>> while ((found = __gang_lookup_nat_cache(nm_i,
>> nid, NATVEC_SIZE, natvec))) {
>> unsigned idx;
>> +
>> + nid = nat_get_nid(natvec[found - 1]) + 1;
>> +
>> for (idx = 0; idx < found; idx++) {
>> struct nat_entry *e = natvec[idx];
>
> Could we replace argument 'e' with 'natvec[idx]'? then we could remove 'e' and
> brace here.
Agree. More neat with this cleanup.
Regards,
Gu
>
> Thanks.
>
>> - nid = nat_get_nid(e) + 1;
>> +
>> __del_from_nat_cache(nm_i, e);
>> }
>> +
>> }
>> f2fs_bug_on(nm_i->nat_cnt);
>> write_unlock(&nm_i->nat_tree_lock);
>> --
>> 1.7.7
>>
>>
>> ------------------------------------------------------------------------------
>> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
>> With Perforce, you get hassle-free workflows. Merge that actually works.
>> Faster operations. Version large binaries. Built-in WAN optimization and the
>> freedom to use Git, Perforce or both. Make the move to Perforce.
>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Linux-f2fs-devel mailing list
>> Linux-f2fs-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>
>
next prev parent reply other threads:[~2014-03-10 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 10:43 [PATCH 1/5] f2fs: update start nid only once each circle Gu Zheng
2014-03-08 11:46 ` [f2fs-dev] " Chao Yu
2014-03-10 1:32 ` Gu Zheng [this message]
2014-03-10 2:26 ` 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=531D161C.8080001@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=chao2.yu@samsung.com \
--cc=jaegeuk.kim@samsung.com \
--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