From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Chao Yu <chao2.yu@samsung.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH V2 2/2 RESEND] f2fs: read contiguous sit entry pages by merging for mount performance
Date: Thu, 21 Nov 2013 18:35:41 +0900 [thread overview]
Message-ID: <1385026541.26319.79.camel@kjgkr> (raw)
In-Reply-To: <000201cee684$550e11a0$ff2a34e0$@samsung.com>
Hi,
> > >
> > > >
> > > > The ra_sit_pages() tries to read consecutive sit pages as many as
> > > > possible.
> > > > So then, what about just checking whether its block address is
> > > > contiguous or not?
> > > >
> > > > Something like this:
> > > > -ra_sit_pages()
> > > > blkno = start;
> > > > while (blkno < sit_i->sit_blocks) {
> > > > blk_addr = current_sit_addr(sbi, blkno);
> > > > if (blkno != start && prev_blk_addr + 1 != blk_addr)
> > > > break;
> > > >
> > > > /* grab and submit_read_page */
> > > >
> > > > prev_blk_addr = blk_addr;
> > > > blkno++;
> > > > }
> > >
> > > Agreed, this method could remove *order.
> > > Shouldn't we add nrpages for readahead policy as VM?
> >
> > Aha, agreed.
> > We need nrpages to avoid too many reads on sit blocks.
> >
> > But, still it needs to change the nrpages in its caller.
> > In your patch, it was sit_i->sit_blocks that is total # of sit blocks.
> > I think 128 or 256 is quite reasonable number.
>
> Hmm, Originally in [PATCH V1] it was be set to
> MAX_BIO_BLOCKS(max_hw_blocks(sbi)).
>
> So it could be "#define SIT_ENTRIES_RA_NUM 128"?
> BTW, maybe we should send dynamical nrpages which depend on
> memory state of system as I mention in previous thread.
> How do you think?
I think it'd be better to use MAX_BIO_BLOCKS().
>
> >
> > Anyway, how about implementing ra_sit_pages() with a blk_plug likewise
> > ra_node_pages()?
My mistake.
This was the ra_nat_pages().
>
> So we use this structure to plug multi bios submitting in ra_sit_pages(), right?
> -build_sit_entries()
> blk_start_plug(&plug);
> ra_sit_pages();
> blk_finish_plug(&plug);
Ah. What I meant was:
blk_start_plug(&plug);
for()
read_sit_page();
blk_finish_plug(&plug);
But, it is not a big deal.
It doesn't matter to use your approach.
Please ignore this.
BTW, I found that we can use submit_read_page() at ra_nat_pages() and
remove block plugging.
I'll send a patch for this. :)
Thanks,
--
Jaegeuk Kim
Samsung
------------------------------------------------------------------------------
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
prev parent reply other threads:[~2013-11-21 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 6:47 [f2fs-dev] [PATCH V2 2/2 RESEND] f2fs: read contiguous sit entry pages by merging for mount performance Chao Yu
2013-11-21 1:31 ` Jaegeuk Kim
2013-11-21 3:18 ` Chao Yu
2013-11-21 4:45 ` Jaegeuk Kim
2013-11-21 6:37 ` [f2fs-dev] " Chao Yu
2013-11-21 9:35 ` Jaegeuk Kim [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=1385026541.26319.79.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=chao2.yu@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).