From: Chao Yu <chao2.yu@samsung.com>
To: jaegeuk.kim@samsung.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
'谭姝' <shu.tan@samsung.com>
Subject: RE: [f2fs-dev] [PATCH V3 2/2] f2fs: read contiguous sit entry pages by merging for mount performance
Date: Mon, 25 Nov 2013 09:33:12 +0800 [thread overview]
Message-ID: <000e01cee97e$6b83e480$428bad80$@samsung.com> (raw)
In-Reply-To: <1385267160.26319.98.camel@kjgkr>
Hi,
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk.kim@samsung.com]
> Sent: Sunday, November 24, 2013 12:26 PM
> To: Chao Yu
> Cc: linux-fsdevel@vger.kernel.org; linux-kernel@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net; 谭姝
> Subject: Re: [f2fs-dev] [PATCH V3 2/2] f2fs: read contiguous sit entry pages by merging for mount performance
>
> Hi,
>
> 2013-11-22 (금), 09:09 +0800, Chao Yu:
> > Previously we read sit entries page one by one, this method lost the chance
> > of reading contiguous page together. So we read pages as contiguous as
> > possible for better mount performance.
> >
> > change log:
> > o merge judgements/use 'Continue' or 'Break' instead of 'Goto' as Gu Zheng
> > suggested.
> > o add mark_page_accessed() before release page to delay VM reclaiming.
> > o remove '*order' for simplification of function as Jaegeuk Kim suggested.
> >
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> > fs/f2fs/segment.c | 103 +++++++++++++++++++++++++++++++++++++++--------------
> > fs/f2fs/segment.h | 2 ++
> > 2 files changed, 78 insertions(+), 27 deletions(-)
> >
> > diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> > index 8149eba..998e7d3 100644
> > --- a/fs/f2fs/segment.c
> > +++ b/fs/f2fs/segment.c
> > @@ -14,6 +14,7 @@
> > #include <linux/blkdev.h>
> > #include <linux/prefetch.h>
> > #include <linux/vmalloc.h>
> > +#include <linux/swap.h>
> >
> > #include "f2fs.h"
> > #include "segment.h"
> > @@ -1488,41 +1489,89 @@ static int build_curseg(struct f2fs_sb_info *sbi)
> > return restore_curseg_summaries(sbi);
> > }
> >
> > +static int ra_sit_pages(struct f2fs_sb_info *sbi, int start, int nrpages)
> > +{
> > + struct address_space *mapping = sbi->meta_inode->i_mapping;
> > + struct page *page;
> > + block_t blk_addr, prev_blk_addr = 0;
> > + int sit_blk_cnt = SIT_BLK_CNT(sbi);
> > + int blkno = start;
> > +
> > + for (; blkno < start + nrpages && blkno < sit_blk_cnt; blkno++) {
> > +
> > + blk_addr = current_sit_addr(sbi, start * SIT_ENTRY_PER_BLOCK);
>
> Should be:
> blk_addr = current_sit_addr(sbi, blkno * SIT_ENTRY_PER_BLOCK);
> -------
> I'll fix this and merge the patch though.
> Thanks,
Oh, It's my mistake, sorry for that.
Thanks for your review! :)
>
> --
> Jaegeuk Kim
> Samsung
prev parent reply other threads:[~2013-11-25 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 1:09 [f2fs-dev] [PATCH V3 2/2] f2fs: read contiguous sit entry pages by merging for mount performance Chao Yu
2013-11-22 9:10 ` Jaegeuk Kim
2013-11-23 2:53 ` Chao Yu
2013-11-24 4:05 ` [f2fs-dev] " Jaegeuk Kim
2013-11-24 4:26 ` Jaegeuk Kim
2013-11-25 1:33 ` Chao Yu [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='000e01cee97e$6b83e480$428bad80$@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 \
--cc=shu.tan@samsung.com \
/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).