From: Yunlong Song <yunlong.song@huawei.com>
To: Chao Yu <yuchao0@huawei.com>, <jaegeuk@kernel.org>,
<chao@kernel.org>, <yunlong.song@icloud.com>
Cc: <miaoxie@huawei.com>, <bintian.wang@huawei.com>,
<linux-fsdevel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] f2fs: let f2fs also gc atomic file to avoid loop gc
Date: Fri, 17 Nov 2017 11:04:36 +0800 [thread overview]
Message-ID: <383339b7-528d-3085-1399-1f1694178c15@huawei.com> (raw)
In-Reply-To: <d5c26f31-2e0c-8b4d-c7f4-b11ff38c20fb@huawei.com>
The atomic commit will trigger:
-f2fs_do_sync_file(filp, 0, LLONG_MAX, 0, true)
-file_write_and_wait_range(file, 0, LLONG_MAX)
-fsync_node_pages
-__write_node_page
-REQ_PREFLUSH | REQ_FUA
So data is flushed to non-volatile before last node write with
REQ_PREFLUSH | REQ_FUA,
we do not need to worry about the inconsistent problem. Right?
On 2017/11/17 10:49, Chao Yu wrote:
> On 2017/11/17 8:58, Yunlong Song wrote:
>> Is there any problem if just deleting the judgement condition in this patch?
> IIRC, dirty node comes from data segment GC can be writebacked & flushed during
> atomic commit, but related data will still be in inner bio cache, after later
> SPOR, data would be inconsistent.
>
> Thanks,
>
>> On 2017/11/8 17:28, Chao Yu wrote:
>>> On 2017/11/8 10:34, Yunlong Song wrote:
>>>> If some files are opened with atomic flag and have not commited yet, at
>>>> the same time, if all the target victim segments have at least one page
>>>> of these atomic files, then f2fs gc will fail to do gc and hangs in the
>>>> process of go to gc_more, since gc_date_segment will not move any data
>>>> and get_valid_blocks will never be 0, then do_garbage_collect will
>>>> always return 0.
>>> Oh, I added this judgment condition to avoid ruining atomic write by data
>>> GC, could we find another way to solve this issue? BTW, if there is direct
>>> IO, we will also skip data segment GC.
>>>
>>> Thanks,
>>>
>>>> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
>>>> ---
>>>> fs/f2fs/gc.c | 6 ------
>>>> 1 file changed, 6 deletions(-)
>>>>
>>>> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
>>>> index 5d5bba4..3fdcd04 100644
>>>> --- a/fs/f2fs/gc.c
>>>> +++ b/fs/f2fs/gc.c
>>>> @@ -621,9 +621,6 @@ static void move_data_block(struct inode *inode, block_t bidx,
>>>> if (!check_valid_map(F2FS_I_SB(inode), segno, off))
>>>> goto out;
>>>>
>>>> - if (f2fs_is_atomic_file(inode))
>>>> - goto out;
>>>> -
>>>> set_new_dnode(&dn, inode, NULL, NULL, 0);
>>>> err = get_dnode_of_data(&dn, bidx, LOOKUP_NODE);
>>>> if (err)
>>>> @@ -718,9 +715,6 @@ static void move_data_page(struct inode *inode, block_t bidx, int gc_type,
>>>> if (!check_valid_map(F2FS_I_SB(inode), segno, off))
>>>> goto out;
>>>>
>>>> - if (f2fs_is_atomic_file(inode))
>>>> - goto out;
>>>> -
>>>> if (gc_type == BG_GC) {
>>>> if (PageWriteback(page))
>>>> goto out;
>>>>
>>> .
>>>
>
> .
>
--
Thanks,
Yunlong Song
next prev parent reply other threads:[~2017-11-17 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 2:34 Yunlong Song
2017-11-08 9:28 ` Chao Yu
2017-11-17 0:58 ` Yunlong Song
2017-11-17 2:49 ` Chao Yu
2017-11-17 3:04 ` Yunlong Song [this message]
2017-11-17 3:20 ` Chao Yu
2017-11-17 3:30 ` Yunlong Song
2017-11-17 5:47 ` Chao Yu
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=383339b7-528d-3085-1399-1f1694178c15@huawei.com \
--to=yunlong.song@huawei.com \
--cc=bintian.wang@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=yuchao0@huawei.com \
--cc=yunlong.song@icloud.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
all inboxes | Powered by JetHome®