From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/7] f2fs: rename free nid cache operation
Date: Tue, 11 Oct 2016 10:19:03 -0700 [thread overview]
Message-ID: <20161011171903.GB82199@jaegeuk> (raw)
In-Reply-To: <20161011143136.2107-3-chao@kernel.org>
Hi Chao,
On Tue, Oct 11, 2016 at 10:31:32PM +0800, Chao Yu wrote:
> From: Chao Yu <yuchao0@huawei.com>
>
> Rename free nid cache operation for readability, no functionality change.
Well, I don't think this can be a *cache*, since there is no cache-related
operations such as reordering by cache hit, whereas it is more likely to
be a singled one-way list.
Thanks,
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> fs/f2fs/node.c | 28 +++++++++++++++++-----------
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> index ea9ff8c..92c9aa4 100644
> --- a/fs/f2fs/node.c
> +++ b/fs/f2fs/node.c
> @@ -1689,13 +1689,19 @@ const struct address_space_operations f2fs_node_aops = {
> #endif
> };
>
> -static struct free_nid *__lookup_free_nid_list(struct f2fs_nm_info *nm_i,
> +static struct free_nid *__lookup_free_nid_cache(struct f2fs_nm_info *nm_i,
> nid_t n)
> {
> return radix_tree_lookup(&nm_i->free_nid_root, n);
> }
>
> -static void __del_from_free_nid_list(struct f2fs_nm_info *nm_i,
> +static int __insert_to_free_nid_cache(struct f2fs_nm_info *nm_i,
> + struct free_nid *i)
> +{
> + return radix_tree_insert(&nm_i->free_nid_root, i->nid, i);
> +}
> +
> +static void __del_from_free_nid_cache(struct f2fs_nm_info *nm_i,
> struct free_nid *i)
> {
> radix_tree_delete(&nm_i->free_nid_root, i->nid);
> @@ -1763,7 +1769,7 @@ static int add_free_nid(struct f2fs_sb_info *sbi, nid_t nid, bool build)
> }
>
> spin_lock(&nm_i->free_nid_list_lock);
> - if (radix_tree_insert(&nm_i->free_nid_root, i->nid, i)) {
> + if (__insert_to_free_nid_cache(nm_i, i)) {
> spin_unlock(&nm_i->free_nid_list_lock);
> radix_tree_preload_end();
> kmem_cache_free(free_nid_slab, i);
> @@ -1782,10 +1788,10 @@ static void remove_free_nid(struct f2fs_sb_info *sbi, nid_t nid)
> bool need_free = false;
>
> spin_lock(&nm_i->free_nid_list_lock);
> - i = __lookup_free_nid_list(nm_i, nid);
> + i = __lookup_free_nid_cache(nm_i, nid);
> if (i && i->state == NID_NEW) {
> __remove_nid_from_list(sbi, i, FREE_NID_LIST);
> - __del_from_free_nid_list(nm_i, i);
> + __del_from_free_nid_cache(nm_i, i);
> need_free = true;
> }
> spin_unlock(&nm_i->free_nid_list_lock);
> @@ -1922,10 +1928,10 @@ void alloc_nid_done(struct f2fs_sb_info *sbi, nid_t nid)
> struct free_nid *i;
>
> spin_lock(&nm_i->free_nid_list_lock);
> - i = __lookup_free_nid_list(nm_i, nid);
> + i = __lookup_free_nid_cache(nm_i, nid);
> f2fs_bug_on(sbi, !i);
> __remove_nid_from_list(sbi, i, ALLOC_NID_LIST);
> - __del_from_free_nid_list(nm_i, i);
> + __del_from_free_nid_cache(nm_i, i);
> spin_unlock(&nm_i->free_nid_list_lock);
>
> kmem_cache_free(free_nid_slab, i);
> @@ -1944,13 +1950,13 @@ void alloc_nid_failed(struct f2fs_sb_info *sbi, nid_t nid)
> return;
>
> spin_lock(&nm_i->free_nid_list_lock);
> - i = __lookup_free_nid_list(nm_i, nid);
> + i = __lookup_free_nid_cache(nm_i, nid);
> f2fs_bug_on(sbi, !i);
>
> __remove_nid_from_list(sbi, i, ALLOC_NID_LIST);
>
> if (!available_free_memory(sbi, FREE_NIDS)) {
> - __del_from_free_nid_list(nm_i, i);
> + __del_from_free_nid_cache(nm_i, i);
> need_free = true;
> } else {
> i->state = NID_NEW;
> @@ -1980,7 +1986,7 @@ int try_to_free_nids(struct f2fs_sb_info *sbi, int nr_shrink)
> break;
>
> __remove_nid_from_list(sbi, i, FREE_NID_LIST);
> - __del_from_free_nid_list(nm_i, i);
> + __del_from_free_nid_cache(nm_i, i);
>
> kmem_cache_free(free_nid_slab, i);
> nr_shrink--;
> @@ -2368,7 +2374,7 @@ void destroy_node_manager(struct f2fs_sb_info *sbi)
> spin_lock(&nm_i->free_nid_list_lock);
> list_for_each_entry_safe(i, next_i, &nm_i->free_nid_list, list) {
> __remove_nid_from_list(sbi, i, FREE_NID_LIST);
> - __del_from_free_nid_list(nm_i, i);
> + __del_from_free_nid_cache(nm_i, i);
> spin_unlock(&nm_i->free_nid_list_lock);
> kmem_cache_free(free_nid_slab, i);
> spin_lock(&nm_i->free_nid_list_lock);
> --
> 2.10.1
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2016-10-11 17:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 14:31 [PATCH 1/7] f2fs: split free nid list Chao Yu
2016-10-11 14:31 ` [PATCH 2/7] f2fs: clean up nid list operation Chao Yu
2016-10-11 14:31 ` [PATCH 3/7] f2fs: rename free nid cache operation Chao Yu
2016-10-11 17:19 ` Jaegeuk Kim [this message]
2016-10-12 15:14 ` Chao Yu
2016-10-12 17:15 ` Jaegeuk Kim
2016-10-13 10:26 ` Chao Yu
2016-10-11 14:31 ` [PATCH 4/7] f2fs: show pending allocated nids count in debugfs Chao Yu
2016-10-11 17:20 ` Jaegeuk Kim
2016-10-11 14:31 ` [PATCH 5/7] f2fs: exclude free nids building and allocation Chao Yu
2016-10-11 17:25 ` Jaegeuk Kim
2016-10-11 14:31 ` [PATCH 6/7] f2fs: don't interrupt free nids building during nid allocation Chao Yu
2016-10-11 14:31 ` [PATCH 7/7] f2fs: avoid casted negative value as shrink count Chao Yu
2016-10-11 17:09 ` [PATCH 1/7] f2fs: split free nid list Jaegeuk Kim
2016-10-12 1:14 ` 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=20161011171903.GB82199@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=chao@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).