From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/5] btrfs: add fs flag to force device flushing
Date: Fri, 16 Jun 2017 06:08:16 +0800 [thread overview]
Message-ID: <e8b99f82-4e39-fda5-39f3-f3349577687d@oracle.com> (raw)
In-Reply-To: <8c201990ae0acb3b80437f9de2e432b60ecf8e4a.1497544265.git.dsterba@suse.com>
On 06/16/2017 12:49 AM, David Sterba wrote:
> We need a device capable of device barriers so we can test the flush
> code. To aid testing, add a per-filesystem status flag that affects the
> barriers regerdless of the device capabilities and obviously does not
> give the same guarantees.
>
> It's off by default, sysfs tunable will follow.
>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
> fs/btrfs/ctree.h | 1 +
> fs/btrfs/disk-io.c | 8 +++++---
> fs/btrfs/volumes.h | 1 +
> 3 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
> index f0f5f28784b6..dcf4404f7d61 100644
> --- a/fs/btrfs/ctree.h
> +++ b/fs/btrfs/ctree.h
> @@ -716,6 +716,7 @@ struct btrfs_delayed_root;
> #define BTRFS_FS_LOG1_ERR 12
> #define BTRFS_FS_LOG2_ERR 13
> #define BTRFS_FS_QUOTA_OVERRIDE 14
> +#define BTRFS_FS_FORCE_DEV_FLUSH 15
>
> /*
> * Indicate that a whole-filesystem exclusive operation is running
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 59a732a13370..659a3b4645d2 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -3494,7 +3494,8 @@ static void write_dev_flush(struct btrfs_device *device)
> struct request_queue *q = bdev_get_queue(device->bdev);
> struct bio *bio = device->flush_bio;
>
> - if (!test_bit(QUEUE_FLAG_WC, &q->queue_flags))
> + if (!test_bit(BTRFS_FS_FORCE_DEV_FLUSH, &device->fs_info->flags)
> + && !test_bit(QUEUE_FLAG_WC, &q->queue_flags))
> return;
Now I understand what you meant. But the most common case in our test
set up is a device with write cache. So BTRFS_FS_FORCE_DEV_FLUSH does
not bring any additional force. IMO.
Thanks, Anand
> bio_reset(bio);
> @@ -3505,6 +3506,7 @@ static void write_dev_flush(struct btrfs_device *device)
> bio->bi_private = &device->flush_wait;
>
> submit_bio(bio);
> + device->flush_bio_sent = 1;
> }
>
> /*
> @@ -3512,12 +3514,12 @@ static void write_dev_flush(struct btrfs_device *device)
> */
> static int wait_dev_flush(struct btrfs_device *device)
> {
> - struct request_queue *q = bdev_get_queue(device->bdev);
> struct bio *bio = device->flush_bio;
>
> - if (!test_bit(QUEUE_FLAG_WC, &q->queue_flags))
> + if (!device->flush_bio_sent)
> return 0;
>
> + device->flush_bio_sent = 0;
> wait_for_completion_io(&device->flush_wait);
>
> return bio->bi_error;
> diff --git a/fs/btrfs/volumes.h b/fs/btrfs/volumes.h
> index 35327efecdbb..6f45fd60d15a 100644
> --- a/fs/btrfs/volumes.h
> +++ b/fs/btrfs/volumes.h
> @@ -75,6 +75,7 @@ struct btrfs_device {
> int can_discard;
> int is_tgtdev_for_dev_replace;
> int last_flush_error;
> + int flush_bio_sent;
>
> #ifdef __BTRFS_NEED_DEVICE_DATA_ORDERED
> seqcount_t data_seqcount;
>
next prev parent reply other threads:[~2017-06-15 22:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 16:49 [PATCH 0/5] Preallocate flush bio, sysfs tunable David Sterba
2017-06-15 16:49 ` [PATCH 1/5] btrfs: preallocate device flush bio David Sterba
2017-06-15 21:53 ` Anand Jain
2017-06-16 13:17 ` David Sterba
2017-06-15 16:49 ` [PATCH 2/5] btrfs: account as waiting for IO, while waiting fot the flush bio completion David Sterba
2017-06-15 16:49 ` [PATCH 3/5] btrfs: move dev stats accounting out of wait_dev_flush David Sterba
2017-06-15 22:00 ` Anand Jain
2017-06-15 16:49 ` [PATCH 4/5] btrfs: add fs flag to force device flushing David Sterba
2017-06-15 22:08 ` Anand Jain [this message]
2017-06-15 22:27 ` Anand Jain
2017-06-16 14:03 ` David Sterba
2017-06-15 16:49 ` [PATCH 5/5] btrfs: sysfs: export the force_dev_flush flag David Sterba
2017-06-15 22:24 ` Anand Jain
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=e8b99f82-4e39-fda5-39f3-f3349577687d@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@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).