Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Liu Song <liusong@linux.alibaba.com>
To:     adilger.kernel@dilger.ca, tytso@mit.edu, jack@suse.cz
Cc:     liusong@linux.alibaba.com, linux-ext4@vger.kernel.org,
        linux-kernel@vger.kernel.org, joseph.qi@linux.alibaba.com
Subject: [PATCH] ext4: do not mark inode dirty which is already dirtied under append-write scenario
Date:   Sun,  6 Aug 2023 11:12:17 +0800
Message-Id: <20230806031217.13962-1-liusong@linux.alibaba.com>
In-Reply-To: <20230711034256.72651-1-liusong@linux.alibaba.com>
References: <20230711034256.72651-1-liusong@linux.alibaba.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi,

Any comments on this? Considering the most extreme scenario
where a file is appended with only one byte each time,
"jbd2_journal_dirty_metadata" will be executed because i_size
has changed. Therefore, it is better to update raw_inode's size
after the writeback is completed, which can also ensure the
consistency of metadata and data, and obtain better performance
benefits in high-frequency append write scenarios.

Thanks