linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Haicheng Li <haicheng.li@linux.intel.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: disable the extent cache ops on high fragmented files
Date: Thu, 21 Nov 2013 13:34:03 +0800	[thread overview]
Message-ID: <20131121053402.GA9143@hli22-desktop> (raw)
In-Reply-To: <1384845037-7872-1-git-send-email-jaegeuk.kim@samsung.com>

> Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>

Function looks good to me. But some nitpicking below for code cleanup..

> @@ -71,6 +71,9 @@ static int check_extent_cache(struct inode *inode, pgoff_t pgofs,
return value could be boolean?
>  	pgoff_t start_fofs, end_fofs;
>  	block_t start_blkaddr;
>  
> +	if (is_inode_flag_set(fi, FI_NO_EXTENT))
> +		return 0;
> +
>  	read_lock(&fi->ext.ext_lock);
>  	if (fi->ext.len == 0) {
>  		read_unlock(&fi->ext.ext_lock);
> @@ -109,6 +112,7 @@ void update_extent_cache(block_t blk_addr, struct dnode_of_data *dn)
>  	struct f2fs_inode_info *fi = F2FS_I(dn->inode);
>  	pgoff_t fofs, start_fofs, end_fofs;
>  	block_t start_blkaddr, end_blkaddr;
> +	int need_update = true;
bool?

      parent reply	other threads:[~2013-11-21  5:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  7:10 [PATCH 1/2] f2fs: disable the extent cache ops on high fragmented files Jaegeuk Kim
2013-11-19  7:10 ` [PATCH 2/2] f2fs: introduce a bio array for per-page write bios Jaegeuk Kim
2013-11-21  5:34 ` Haicheng Li [this message]

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=20131121053402.GA9143@hli22-desktop \
    --to=haicheng.li@linux.intel.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).