From: yebin <yebin10@huawei.com>
To: Jan Kara <jack@suse.cz>
Cc: <tytso@mit.edu>, <adilger.kernel@dilger.ca>,
<linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next 2/2] ext4: adjust fast commit disable judgement order in ext4_fc_track_inode
Date: Thu, 15 Sep 2022 22:42:58 +0800 [thread overview]
Message-ID: <632339F2.1000802@huawei.com> (raw)
In-Reply-To: <20220915143008.27woacjur6sg32t2@quack3>
On 2022/9/15 22:30, Jan Kara wrote:
> On Thu 15-09-22 21:56:11, Ye Bin wrote:
>> Judge filesystem if fast commit disabled before test inode's journal mode.
>>
>> Signed-off-by: Ye Bin <yebin10@huawei.com>
> Probably makes sense but is there any particular reason why you do this?
>
> Honza
I think the impact of fast commit on normal processes should be minimized.
>
>> ---
>> fs/ext4/fast_commit.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
>> index eadab945b856..9217a588afd1 100644
>> --- a/fs/ext4/fast_commit.c
>> +++ b/fs/ext4/fast_commit.c
>> @@ -577,15 +577,15 @@ void ext4_fc_track_inode(handle_t *handle, struct inode *inode)
>> if (S_ISDIR(inode->i_mode))
>> return;
>>
>> + if (ext4_fc_disabled(inode->i_sb))
>> + return;
>> +
>> if (ext4_should_journal_data(inode)) {
>> ext4_fc_mark_ineligible(inode->i_sb,
>> EXT4_FC_REASON_INODE_JOURNAL_DATA, handle);
>> return;
>> }
>>
>> - if (ext4_fc_disabled(inode->i_sb))
>> - return;
>> -
>> if (ext4_test_mount_flag(inode->i_sb, EXT4_MF_FC_INELIGIBLE))
>> return;
>>
>> --
>> 2.31.1
>>
next prev parent reply other threads:[~2022-09-15 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 13:56 [PATCH -next 0/2] some refactor of ext4_fc_track_inode Ye Bin
2022-09-15 13:56 ` [PATCH -next 1/2] ext4: factor out ext4_fc_disabled() Ye Bin
2022-09-15 14:29 ` Jan Kara
2022-09-15 13:56 ` [PATCH -next 2/2] ext4: adjust fast commit disable judgement order in ext4_fc_track_inode Ye Bin
2022-09-15 14:30 ` Jan Kara
2022-09-15 14:42 ` yebin [this message]
2022-09-15 14:51 ` Jan Kara
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=632339F2.1000802@huawei.com \
--to=yebin10@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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