From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: use f2fs_submit_page_bio for ra_meta_pages
Date: Thu, 11 May 2017 11:22:23 +0800 [thread overview]
Message-ID: <2e1c8d7b-4494-29c3-1f6b-e181f2e312a5@huawei.com> (raw)
In-Reply-To: <20170511024123.GB3967@jaegeuk.local>
On 2017/5/11 10:41, Jaegeuk Kim wrote:
> On 05/11, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2017/5/11 7:48, Jaegeuk Kim wrote:
>>> This patch avoids to use f2fs_submit_merged_bio for read, which was the only
>>> read case.
>>
>> This makes f2fs losing the chance to merge multiple pages into one bio during
>> reading continuous physical blocks, it may cause potential performance
>> regression, how about using a local bio in ra_meta_pages to cache more pages?
>
> This is a readahead flow, which is asynchronous and not a performance critical
> flow. And, I expect blk_plug is still able to merge them. We're using this in
> readahead of node blocks as well.
Confirmed, block plug can do the merge. :)
Thanks,
>
> Thanks,
>
>>
>> Thanks,
>>
>>>
>>> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>>> ---
>>> fs/f2fs/checkpoint.c | 4 +---
>>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>>
>>> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
>>> index ea9c317b5916..8d92f8249000 100644
>>> --- a/fs/f2fs/checkpoint.c
>>> +++ b/fs/f2fs/checkpoint.c
>>> @@ -207,12 +207,10 @@ int ra_meta_pages(struct f2fs_sb_info *sbi, block_t start, int nrpages,
>>> }
>>>
>>> fio.page = page;
>>> - fio.old_blkaddr = fio.new_blkaddr;
>>> - f2fs_submit_page_mbio(&fio);
>>> + f2fs_submit_page_bio(&fio);
>>> f2fs_put_page(page, 0);
>>> }
>>> out:
>>> - f2fs_submit_merged_bio(sbi, META, READ);
>>> blk_finish_plug(&plug);
>>> return blkno - start;
>>> }
>>>
>
> .
>
prev parent reply other threads:[~2017-05-11 3:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 23:48 Jaegeuk Kim
2017-05-10 23:48 ` [PATCH 2/3] f2fs: remove unnecessary read cases in merged IO flow Jaegeuk Kim
2017-05-10 23:48 ` [PATCH 3/3] f2fs: use fio instead of multiple parameters Jaegeuk Kim
2017-05-11 1:24 ` [f2fs-dev] [PATCH 1/3] f2fs: use f2fs_submit_page_bio for ra_meta_pages Chao Yu
2017-05-11 1:47 ` Chao Yu
2017-05-11 2:41 ` Jaegeuk Kim
2017-05-11 2:41 ` Jaegeuk Kim
2017-05-11 3:22 ` 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=2e1c8d7b-4494-29c3-1f6b-e181f2e312a5@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--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
all inboxes | Powered by JetHome®