From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <chao@kernel.org>
Subject: Re: [PATCH v2] f2fs: restrict write IO alignment condition
Date: Tue, 14 Mar 2017 19:32:16 +0800 [thread overview]
Message-ID: <07e43857-1387-eb9b-478d-57d2f14d81e4@huawei.com> (raw)
In-Reply-To: <20170313200544.GE41055@jaegeuk.local>
On 2017/3/14 4:05, Jaegeuk Kim wrote:
> On 03/13, Chao Yu wrote:
>> We should only align start offset of bio with defined IO_SIZE for below
>> conditions:
>> a. mode=lfs mount option
>> b. write IOs
>> c. Out-place-update
>> d. non-meta pages
>>
>> Signed-off-by: Chao Yu <yuchao0@huawei.com>
>> ---
>> fs/f2fs/data.c | 10 +++++++---
>> 1 file changed, 7 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
>> index 1375fef11146..53fe79c70406 100644
>> --- a/fs/f2fs/data.c
>> +++ b/fs/f2fs/data.c
>> @@ -190,6 +190,9 @@ static inline void __submit_bio(struct f2fs_sb_info *sbi,
>> current->plug && (type == DATA || type == NODE))
>> blk_finish_plug(current->plug);
>>
>> + if (!test_opt(sbi, LFS))
>> + goto submit_io;
>
> The parse_options in fill_super checks this.
You're right, I missed that one...
>
>> +
>> if (type != DATA && type != NODE)
>> goto submit_io;
>>
>> @@ -395,11 +398,12 @@ int f2fs_submit_page_mbio(struct f2fs_io_info *fio)
>> __submit_merged_bio(io);
>> alloc_new:
>> if (io->bio == NULL) {
>> - if ((fio->type == DATA || fio->type == NODE) &&
>> + if (test_opt(sbi, LFS) &&
>> + !is_read && (fio->type == DATA || fio->type == NODE) &&
>
> The missing case is !is_read, here?
> But, actually, DATA and NODE don't issue any read commands at all.
Correct, let me add BUG_ON here. :)
Thanks,
>
> Thanks,
>
>> fio->new_blkaddr & F2FS_IO_SIZE_MASK(sbi)) {
>> err = -EAGAIN;
>> - if (!is_read)
>> - dec_page_count(sbi, WB_DATA_TYPE(bio_page));
>> + f2fs_bug_on(sbi, fio->new_blkaddr == fio->old_blkaddr);
>> + dec_page_count(sbi, WB_DATA_TYPE(bio_page));
>> goto out_fail;
>> }
>> io->bio = __bio_alloc(sbi, fio->new_blkaddr,
>> --
>> 2.8.2.295.g3f1c1d0
>
> .
>
prev parent reply other threads:[~2017-03-14 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 13:02 Chao Yu
2017-03-13 13:45 ` [f2fs-dev] " Kinglong Mee
2017-03-13 20:05 ` Jaegeuk Kim
2017-03-14 11:32 ` 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=07e43857-1387-eb9b-478d-57d2f14d81e4@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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®