From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org, linux-block@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [RFC PATCH 0/2] Introduce blkdev_issue_flush_no_wait()
Date: Tue, 16 May 2017 17:39:12 +0800 [thread overview]
Message-ID: <20170516093914.16035-1-anand.jain@oracle.com> (raw)
BTRFS wanted a block device flush function which does not wait for
its completion, so that the flush for the next device can be called
in the same thread.
Here is a RFC patch to provide the function
'blkdev_issue_flush_no_wait()', which is based on the current device
flush function 'blkdev_issue_flush()', however it uses submit_bio()
instead of submit_bio_wait().
This patch is for review comments, will send out a final patch based
on the comments received.
Thanks, Anand
Anand Jain (2):
block: Introduce blkdev_issue_flush_no_wait()
btrfs: Use blkdev_issue_flush_no_wait()
block/blk-flush.c | 47 +++++++++++++++++++++
fs/btrfs/disk-io.c | 108 +++++++++++++++----------------------------------
fs/btrfs/volumes.h | 2 +-
include/linux/blkdev.h | 8 ++++
4 files changed, 88 insertions(+), 77 deletions(-)
--
2.10.0
next reply other threads:[~2017-05-16 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 9:39 Anand Jain [this message]
2017-05-16 9:39 ` [PATCH 1/2] block: Introduce blkdev_issue_flush_no_wait() Anand Jain
2017-05-16 11:56 ` Christoph Hellwig
2017-05-18 9:31 ` Anand Jain
2017-05-21 7:09 ` Christoph Hellwig
2017-05-24 8:42 ` Anand Jain
2017-05-16 9:39 ` [PATCH 2/2] btrfs: Use blkdev_issue_flush_no_wait() Anand Jain
2017-05-16 12:00 ` Christoph Hellwig
2017-05-16 14:07 ` [RFC PATCH 0/2] Introduce blkdev_issue_flush_no_wait() Bart Van Assche
2017-05-17 17:14 ` David Sterba
2017-05-18 9:31 ` Anand Jain
2017-05-18 9:27 ` 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=20170516093914.16035-1-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-block@vger.kernel.org \
--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).