linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Changman Lee <cm224.lee@samsung.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: [PATCH] f2fs: merge read IOs at ra_nat_pages()
Date: Fri, 22 Nov 2013 12:41:19 +0900	[thread overview]
Message-ID: <1385091679.16054.5.camel@lcm> (raw)
In-Reply-To: <1385026550-21055-1-git-send-email-jaegeuk.kim@samsung.com>


How about doing mark_page_accessed(page) in ra_nat_pages like
ra_sit_pages to prevent readahead pages are reclaimed by VM?

On 목, 2013-11-21 at 18:35 +0900, Jaegeuk Kim wrote:
> This patch changes the policy of submitting read bios at ra_nat_pages.
> 
> Previously, f2fs submits small read bios with block plugging.
> But, with this patch, f2fs itself merges read bios first and then submits a
> large bio, which can reduce the bio handling overheads.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
> ---
>  fs/f2fs/node.c | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> index b843a5b..c06871f 100644
> --- a/fs/f2fs/node.c
> +++ b/fs/f2fs/node.c
> @@ -89,13 +89,10 @@ static void ra_nat_pages(struct f2fs_sb_info *sbi, int nid)
>  {
>  	struct address_space *mapping = sbi->meta_inode->i_mapping;
>  	struct f2fs_nm_info *nm_i = NM_I(sbi);
> -	struct blk_plug plug;
>  	struct page *page;
>  	pgoff_t index;
>  	int i;
>  
> -	blk_start_plug(&plug);
> -
>  	for (i = 0; i < FREE_NID_PAGES; i++, nid += NAT_ENTRY_PER_BLOCK) {
>  		if (nid >= nm_i->max_nid)
>  			nid = 0;
> @@ -108,12 +105,11 @@ static void ra_nat_pages(struct f2fs_sb_info *sbi, int nid)

mark_page_accessed(page);

>  			f2fs_put_page(page, 1);
>  			continue;
>  		}
> -		if (f2fs_readpage(sbi, page, index, READ))
> -			continue;
> +		submit_read_page(sbi, page, index, READ_SYNC);
>  

mark_page_accessed(page);

>  		f2fs_put_page(page, 0);
>  	}
> -	blk_finish_plug(&plug);
> +	f2fs_submit_read_bio(sbi, READ_SYNC);
>  }
>  
>  static struct nat_entry *__lookup_nat_cache(struct f2fs_nm_info *nm_i, nid_t n)



------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2013-11-22  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  9:35 [PATCH] f2fs: merge read IOs at ra_nat_pages() Jaegeuk Kim
2013-11-22  3:41 ` Changman Lee [this message]
2013-11-24  2:46   ` [f2fs-dev] " 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=1385091679.16054.5.camel@lcm \
    --to=cm224.lee@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).