From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/7] f2fs: Make flush bios explicitely sync
Date: Wed, 3 May 2017 14:22:46 -0700 [thread overview]
Message-ID: <20170503212246.GA97544@jaegeuk.local> (raw)
In-Reply-To: <20170502150351.29452-4-jack@suse.cz>
Hi Jan,
On 05/02, Jan Kara wrote:
> Commit b685d3d65ac7 "block: treat REQ_FUA and REQ_PREFLUSH as
> synchronous" removed REQ_SYNC flag from WRITE_{FUA|PREFLUSH|...}
> definitions. generic_make_request_checks() however strips REQ_FUA and
> REQ_PREFLUSH flags from a bio when the storage doesn't report volatile
> write cache and thus write effectively becomes asynchronous which can
> lead to performance regressions.
>
> Fix the problem by making sure all bios which are synchronous are
> properly marked with REQ_SYNC.
>
> Fixes: b685d3d65ac791406e0dfd8779cc9b3707fea5a3
Looks good to me. Thank you for the patch.
BTW, does this need cc to stable?
Cc: stable@vger.kernel.org # 4.9+
Thanks,
> CC: Jaegeuk Kim <jaegeuk@kernel.org>
> CC: linux-f2fs-devel@lists.sourceforge.net
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/f2fs/data.c | 2 +-
> fs/f2fs/segment.c | 2 +-
> fs/f2fs/super.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 1602b4bccae6..dd24476e8d2c 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -309,7 +309,7 @@ static void __f2fs_submit_merged_bio(struct f2fs_sb_info *sbi,
> if (type >= META_FLUSH) {
> io->fio.type = META_FLUSH;
> io->fio.op = REQ_OP_WRITE;
> - io->fio.op_flags = REQ_META | REQ_PRIO;
> + io->fio.op_flags = REQ_META | REQ_PRIO | REQ_SYNC;
> if (!test_opt(sbi, NOBARRIER))
> io->fio.op_flags |= REQ_PREFLUSH | REQ_FUA;
> }
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 29ef7088c558..0c24cec55dc9 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -416,7 +416,7 @@ static int __submit_flush_wait(struct block_device *bdev)
> struct bio *bio = f2fs_bio_alloc(0);
> int ret;
>
> - bio->bi_opf = REQ_OP_WRITE | REQ_PREFLUSH;
> + bio->bi_opf = REQ_OP_WRITE | REQ_SYNC | REQ_PREFLUSH;
> bio->bi_bdev = bdev;
> ret = submit_bio_wait(bio);
> bio_put(bio);
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index 96fe8ed73100..fa5af1f04798 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -1307,7 +1307,7 @@ static int __f2fs_commit_super(struct buffer_head *bh,
> unlock_buffer(bh);
>
> /* it's rare case, we can do fua all the time */
> - return __sync_dirty_buffer(bh, REQ_PREFLUSH | REQ_FUA);
> + return __sync_dirty_buffer(bh, REQ_SYNC | REQ_PREFLUSH | REQ_FUA);
> }
>
> static inline bool sanity_check_area_boundary(struct f2fs_sb_info *sbi,
> --
> 2.12.0
next prev parent reply other threads:[~2017-05-03 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 15:03 [PATCH 0/7] Fix fallout from changes to FUA and PREFLUSH definitions Jan Kara
2017-05-02 15:03 ` [PATCH 3/7] f2fs: Make flush bios explicitely sync Jan Kara
2017-05-03 16:20 ` [f2fs-dev] " Chao Yu
2017-05-03 21:22 ` Jaegeuk Kim [this message]
2017-05-04 7:32 ` Jan Kara
2017-05-04 7:34 ` Jan Kara
2017-05-04 7:36 ` Jaegeuk Kim
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=20170503212246.GA97544@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
/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).