linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao2.yu@samsung.com>
To: jaegeuk.kim@samsung.com
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: [f2fs-dev] [PATCH] f2fs: fix to enable readahead last NAT block
Date: Fri, 18 Apr 2014 11:17:16 +0800	[thread overview]
Message-ID: <000901cf5ab4$d64171a0$82c454e0$@samsung.com> (raw)
In-Reply-To: <1397787344.7727.32.camel@kjgkr>

Hi,

> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk.kim@samsung.com]
> Sent: Friday, April 18, 2014 10:16 AM
> To: Chao Yu
> Cc: linux-f2fs-devel@lists.sourceforge.net; linux-fsdevel@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to enable readahead last NAT block
> 
> Hi Chao,
> 
> How about this?

This modification can really fix the previously deadloop problem without bringing
more problem. I'd like use your patch.
Thanks.

One comment as following.

Reviewed-by: Chao Yu <chao2.yu@samsung.com>

> 
> ---
>  fs/f2fs/f2fs.h | 1 +
>  fs/f2fs/node.c | 6 ++++--
>  2 files changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index 55152de..556d06b 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -244,6 +244,7 @@ static inline void set_raw_extent(struct extent_info
> *ext,
>  struct f2fs_nm_info {
>  	block_t nat_blkaddr;		/* base disk address of NAT */
>  	nid_t max_nid;			/* maximum possible node ids */
> +	nid_t available_nids;		/* maximum available node ids */
>  	nid_t next_scan_nid;		/* the next nid to be scanned */
>  	unsigned int ram_thresh;	/* control the memory footprint */
> 
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> index 837f5fd..5fb484c 100644
> --- a/fs/f2fs/node.c
> +++ b/fs/f2fs/node.c
> @@ -1447,7 +1447,7 @@ bool alloc_nid(struct f2fs_sb_info *sbi, nid_t
> *nid)
>  	struct f2fs_nm_info *nm_i = NM_I(sbi);
>  	struct free_nid *i = NULL;
>  retry:
> -	if (unlikely(sbi->total_valid_node_count + 1 >= nm_i->max_nid))
> +	if (unlikely(sbi->total_valid_node_count + 1 >= nm_i->available_nids))

Could we use the last valid nid and modify like this?

	if (unlikely(sbi->total_valid_node_count + 1 > nm_i->available_nids))

>  		return false;
> 
>  	spin_lock(&nm_i->free_nid_list_lock);
> @@ -1859,8 +1859,10 @@ static int init_node_manager(struct f2fs_sb_info
> *sbi)
>  	nat_segs = le32_to_cpu(sb_raw->segment_count_nat) >> 1;
>  	nat_blocks = nat_segs << le32_to_cpu(sb_raw->log_blocks_per_seg);
> 
> +	nm_i->max_nid = NAT_ENTRY_PER_BLOCK * nat_blocks;
> +
>  	/* not used nids: 0, node, meta, (and root counted as valid node) */
> -	nm_i->max_nid = NAT_ENTRY_PER_BLOCK * nat_blocks - 3;
> +	nm_i->available_nids = nm_i->max_nid - 3;
>  	nm_i->fcnt = 0;
>  	nm_i->nat_cnt = 0;
>  	nm_i->ram_thresh = DEF_RAM_THRESHOLD;
> --
> 1.8.4.474.g128a96c
> 
> 
> --
> Jaegeuk Kim
> Samsung

  reply	other threads:[~2014-04-18  3:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17  9:20 [PATCH] f2fs: fix to enable readahead last NAT block Chao Yu
2014-04-18  2:15 ` [f2fs-dev] " Jaegeuk Kim
2014-04-18  3:17   ` Chao Yu [this message]
2014-04-18  5:58     ` 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='000901cf5ab4$d64171a0$82c454e0$@samsung.com' \
    --to=chao2.yu@samsung.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).