All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Zhang Yi <yi.zhang@huawei.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
	adilger.kernel@dilger.ca, jack@suse.cz, yukuai3@huawei.com
Subject: Re: [PATCH v2 1/4] ext4: check and update i_disksize properly
Date: Thu, 15 Jul 2021 13:52:01 +0200	[thread overview]
Message-ID: <20210715115201.GE9457@quack2.suse.cz> (raw)
In-Reply-To: <20210715015452.2542505-2-yi.zhang@huawei.com>

On Thu 15-07-21 09:54:49, Zhang Yi wrote:
> After commit 3da40c7b0898 ("ext4: only call ext4_truncate when size <=
> isize"), i_disksize could always be updated to i_size in ext4_setattr(),
> and we could sure that i_disksize <= i_size since holding inode lock and
> if i_disksize < i_size there are delalloc writes pending in the range
> upto i_size. If the end of the current write is <= i_size, there's no
> need to touch i_disksize since writeback will push i_disksize upto
> i_size eventually. So we can switch to check i_size instead of
> i_disksize in ext4_da_write_end() when write to the end of the file.
> we also could remove ext4_mark_inode_dirty() together because we defer
> inode dirtying to generic_write_end() or ext4_da_write_inline_data_end().
> 
> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>

Looks good. Feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  fs/ext4/inode.c | 34 ++++++++++++++++++----------------
>  1 file changed, 18 insertions(+), 16 deletions(-)
> 
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index d8de607849df..dca8e3810443 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -3084,35 +3084,37 @@ static int ext4_da_write_end(struct file *file,
>  	end = start + copied - 1;
>  
>  	/*
> -	 * generic_write_end() will run mark_inode_dirty() if i_size
> -	 * changes.  So let's piggyback the i_disksize mark_inode_dirty
> -	 * into that.
> +	 * Since we are holding inode lock, we are sure i_disksize <=
> +	 * i_size. We also know that if i_disksize < i_size, there are
> +	 * delalloc writes pending in the range upto i_size. If the end of
> +	 * the current write is <= i_size, there's no need to touch
> +	 * i_disksize since writeback will push i_disksize upto i_size
> +	 * eventually. If the end of the current write is > i_size and
> +	 * inside an allocated block (ext4_da_should_update_i_disksize()
> +	 * check), we need to update i_disksize here as neither
> +	 * ext4_writepage() nor certain ext4_writepages() paths not
> +	 * allocating blocks update i_disksize.
> +	 *
> +	 * Note that we defer inode dirtying to generic_write_end() /
> +	 * ext4_da_write_inline_data_end().
>  	 */
>  	new_i_size = pos + copied;
> -	if (copied && new_i_size > EXT4_I(inode)->i_disksize) {
> +	if (copied && new_i_size > inode->i_size) {
>  		if (ext4_has_inline_data(inode) ||
> -		    ext4_da_should_update_i_disksize(page, end)) {
> +		    ext4_da_should_update_i_disksize(page, end))
>  			ext4_update_i_disksize(inode, new_i_size);
> -			/* We need to mark inode dirty even if
> -			 * new_i_size is less that inode->i_size
> -			 * bu greater than i_disksize.(hint delalloc)
> -			 */
> -			ret = ext4_mark_inode_dirty(handle, inode);
> -		}
>  	}
>  
>  	if (write_mode != CONVERT_INLINE_DATA &&
>  	    ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA) &&
>  	    ext4_has_inline_data(inode))
> -		ret2 = ext4_da_write_inline_data_end(inode, pos, len, copied,
> +		ret = ext4_da_write_inline_data_end(inode, pos, len, copied,
>  						     page);
>  	else
> -		ret2 = generic_write_end(file, mapping, pos, len, copied,
> +		ret = generic_write_end(file, mapping, pos, len, copied,
>  							page, fsdata);
>  
> -	copied = ret2;
> -	if (ret2 < 0)
> -		ret = ret2;
> +	copied = ret;
>  	ret2 = ext4_journal_stop(handle);
>  	if (unlikely(ret2 && !ret))
>  		ret = ret2;
> -- 
> 2.31.1
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2021-07-15 11:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15  1:54 [PATCH v2 0/4] ext4: improve delalloc buffer write performance Zhang Yi
2021-07-15  1:54 ` [PATCH v2 1/4] ext4: check and update i_disksize properly Zhang Yi
2021-07-15 11:52   ` Jan Kara [this message]
2021-07-15  1:54 ` [PATCH v2 2/4] ext4: correct the error path of ext4_write_inline_data_end() Zhang Yi
2021-07-15  1:54 ` [PATCH v2 3/4] ext4: factor out write end code of inline file Zhang Yi
2021-07-15 12:08   ` Jan Kara
2021-07-16  3:56     ` Zhang Yi
2021-07-16 10:08       ` Jan Kara
2021-07-16 12:04         ` Zhang Yi
2021-07-15  1:54 ` [PATCH v2 4/4] ext4: drop unnecessary journal handle in delalloc write Zhang Yi

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=20210715115201.GE9457@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@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.