linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Daejun Park <daejun7.park@samsung.com>
Cc: "tytso@mit.edu" <tytso@mit.edu>,
	"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
	"harshadshirwadkar@gmail.com" <harshadshirwadkar@gmail.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ext4: Remove expensive flush on fast commit
Date: Wed, 6 Jan 2021 14:05:26 -0800	[thread overview]
Message-ID: <20210106220526.GH6908@magnolia> (raw)
In-Reply-To: <20210106013242epcms2p5b6b4ed8ca86f29456fdf56aa580e74b4@epcms2p5>

On Wed, Jan 06, 2021 at 10:32:42AM +0900, Daejun Park wrote:
> In the fast commit, it adds REQ_FUA and REQ_PREFLUSH on each fast commit
> block when barrier is enabled. However, in recovery phase, ext4 compares
> CRC value in the tail. So it is sufficient adds REQ_FUA and REQ_PREFLUSH
> on the block that has tail.

Just out of curiosity, how does the new fastcommit code handle tests
like generic/475 that simulate sudden disk failure?

--D

> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
> ---
>  fs/ext4/fast_commit.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
> index 4fcc21c25e79..e66507be334c 100644
> --- a/fs/ext4/fast_commit.c
> +++ b/fs/ext4/fast_commit.c
> @@ -604,13 +604,13 @@ void ext4_fc_track_range(handle_t *handle, struct inode *inode, ext4_lblk_t star
>  	trace_ext4_fc_track_range(inode, start, end, ret);
>  }
>  
> -static void ext4_fc_submit_bh(struct super_block *sb)
> +static void ext4_fc_submit_bh(struct super_block *sb, bool is_tail)
>  {
>  	int write_flags = REQ_SYNC;
>  	struct buffer_head *bh = EXT4_SB(sb)->s_fc_bh;
>  
> -	/* TODO: REQ_FUA | REQ_PREFLUSH is unnecessarily expensive. */
> -	if (test_opt(sb, BARRIER))
> +	/* Add REQ_FUA | REQ_PREFLUSH only its tail */
> +	if (test_opt(sb, BARRIER) && is_tail)
>  		write_flags |= REQ_FUA | REQ_PREFLUSH;
>  	lock_buffer(bh);
>  	set_buffer_dirty(bh);
> @@ -684,7 +684,7 @@ static u8 *ext4_fc_reserve_space(struct super_block *sb, int len, u32 *crc)
>  		*crc = ext4_chksum(sbi, *crc, tl, sizeof(*tl));
>  	if (pad_len > 0)
>  		ext4_fc_memzero(sb, tl + 1, pad_len, crc);
> -	ext4_fc_submit_bh(sb);
> +	ext4_fc_submit_bh(sb, false);
>  
>  	ret = jbd2_fc_get_buf(EXT4_SB(sb)->s_journal, &bh);
>  	if (ret)
> @@ -741,7 +741,7 @@ static int ext4_fc_write_tail(struct super_block *sb, u32 crc)
>  	tail.fc_crc = cpu_to_le32(crc);
>  	ext4_fc_memcpy(sb, dst, &tail.fc_crc, sizeof(tail.fc_crc), NULL);
>  
> -	ext4_fc_submit_bh(sb);
> +	ext4_fc_submit_bh(sb, true);
>  
>  	return 0;
>  }
> -- 
> 2.25.1
> 

  parent reply	other threads:[~2021-01-06 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210106013242epcms2p5b6b4ed8ca86f29456fdf56aa580e74b4@epcms2p5>
2021-01-06  1:32 ` [PATCH] ext4: Remove expensive flush on fast commit Daejun Park
2021-01-06 21:58   ` harshad shirwadkar
2021-01-08  2:26     ` Andreas Dilger
     [not found]     ` <CGME20210106013242epcms2p5b6b4ed8ca86f29456fdf56aa580e74b4@epcms2p3>
2021-01-08  2:37       ` Daejun Park
2021-01-06 22:05   ` Darrick J. Wong [this message]
2021-01-14  3:44   ` Theodore Ts'o

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=20210106220526.GH6908@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=daejun7.park@samsung.com \
    --cc=harshadshirwadkar@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).