All of lore.kernel.org
 help / color / mirror / Atom feed
From: heyunlei <heyunlei@huawei.com>
To: "Yuchao (T)" <yuchao0@huawei.com>,
	"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Cc: "Zhangdianfang (Euler)" <zhangdianfang@huawei.com>
Subject: Re: [PATCH] f2fs: allocate hot_data for atomic write more strictly
Date: Tue, 17 Apr 2018 09:14:22 +0000	[thread overview]
Message-ID: <42B685BFA705F94C860C6DD0752F056548373AE8@DGGEMA503-MBS.china.huawei.com> (raw)
In-Reply-To: <16d8fe6b-5e48-2723-b7df-7f199ecb499c@huawei.com>



>-----Original Message-----
>From: Yuchao (T)
>Sent: Tuesday, April 17, 2018 4:31 PM
>To: heyunlei; jaegeuk@kernel.org; linux-f2fs-devel@lists.sourceforge.net
>Cc: Wangbintian; Zhangdianfang (Euler)
>Subject: Re: [f2fs-dev][PATCH] f2fs: allocate hot_data for atomic write more strictly
>
>On 2018/4/16 19:34, Yunlei He wrote:
>> If a file not set type as hot, has dirty pages more than
>> threshold 64 before starting atomic write, may be lose hot
>> flag.
>>
>> Signed-off-by: Yunlei He <heyunlei@huawei.com>
>> ---
>>  fs/f2fs/file.c | 3 +--
>>  1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
>> index 79eeed5..bf61e20 100644
>> --- a/fs/f2fs/file.c
>> +++ b/fs/f2fs/file.c
>> @@ -1685,7 +1685,6 @@ static int f2fs_ioc_start_atomic_write(struct file *filp)
>>  		goto out;
>>
>>  	set_inode_flag(inode, FI_ATOMIC_FILE);
>
>How about moving this below inc_stat tag? If there is still dirty page, for
>reclaim path, we may redirty page with atomic write mode, we need to avoid that.
>
With it,maybe still has dirty pages after filemap_write_and_wait_range,
which are not inmem pages and maybe affect atomicity?

Thanks.

>> -	set_inode_flag(inode, FI_HOT_DATA);
>>  	f2fs_update_time(F2FS_I_SB(inode), REQ_TIME);
>
>Ditto.
>
>Thanks,
>
>>
>>  	if (!get_dirty_pages(inode))
>> @@ -1697,11 +1696,11 @@ static int f2fs_ioc_start_atomic_write(struct file *filp)
>>  	ret = filemap_write_and_wait_range(inode->i_mapping, 0, LLONG_MAX);
>>  	if (ret) {
>>  		clear_inode_flag(inode, FI_ATOMIC_FILE);
>> -		clear_inode_flag(inode, FI_HOT_DATA);
>>  		goto out;
>>  	}
>>
>>  inc_stat:
>> +	set_inode_flag(inode, FI_HOT_DATA);
>>  	F2FS_I(inode)->inmem_task = current;
>>  	stat_inc_atomic_write(inode);
>>  	stat_update_max_atomic_write(inode);
>>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2018-04-17  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 11:34 [PATCH] f2fs: allocate hot_data for atomic write more strictly Yunlei He
2018-04-17  8:30 ` Chao Yu
2018-04-17  9:14   ` heyunlei [this message]
2018-04-17  9:52     ` 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=42B685BFA705F94C860C6DD0752F056548373AE8@DGGEMA503-MBS.china.huawei.com \
    --to=heyunlei@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=yuchao0@huawei.com \
    --cc=zhangdianfang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.