linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Cc: adilger@dilger.ca, Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 09/10] btrfs: add support for passing in stream information for buffered writes
Date: Tue, 13 Jun 2017 22:01:58 -0600	[thread overview]
Message-ID: <1497412919-19400-10-git-send-email-axboe@kernel.dk> (raw)
In-Reply-To: <1497412919-19400-1-git-send-email-axboe@kernel.dk>

Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
---
 fs/btrfs/extent_io.c | 1 +
 fs/btrfs/inode.c     | 1 +
 2 files changed, 2 insertions(+)

diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index d3619e010005..b245085e8f10 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -2827,6 +2827,7 @@ static int submit_extent_page(int op, int op_flags, struct extent_io_tree *tree,
 	bio->bi_end_io = end_io_func;
 	bio->bi_private = tree;
 	bio_set_op_attrs(bio, op, op_flags);
+	bio_set_streamid(bio, inode_streamid(page->mapping->host));
 	if (wbc) {
 		wbc_init_bio(wbc, bio);
 		wbc_account_io(wbc, page, page_size);
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index ef3c98c527c1..db0558a19f65 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -8608,6 +8608,7 @@ static void btrfs_submit_direct(struct bio *dio_bio, struct inode *inode,
 	atomic_set(&dip->pending_bios, 0);
 	btrfs_bio = btrfs_io_bio(io_bio);
 	btrfs_bio->logical = file_offset;
+	bio_set_streamid(io_bio, bio_stream(dio_bio));
 
 	if (write) {
 		io_bio->bi_end_io = btrfs_endio_direct_write;
-- 
2.7.4

  parent reply	other threads:[~2017-06-14  4:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  4:01 [PATCHSET v2] Add support for write life time hints Jens Axboe
2017-06-14  4:01 ` [PATCH 01/10] block: add support for carrying stream information in a bio Jens Axboe
2017-06-14  4:01 ` [PATCH 02/10] blk-mq: expose stream write stats through debugfs Jens Axboe
2017-06-14  4:07   ` Andreas Dilger
2017-06-14  4:01 ` [PATCH 03/10] fs: add support for an inode to carry stream related data Jens Axboe
2017-06-14  4:01 ` [PATCH 04/10] fs: add support for allowing applications to pass in write life time hints Jens Axboe
2017-06-14  4:06   ` Andreas Dilger
2017-06-14  4:01 ` [PATCH 05/10] fs: add O_DIRECT support for sending down bio stream information Jens Axboe
2017-06-14  4:01 ` [PATCH 06/10] fs: add support for buffered writeback to pass down " Jens Axboe
2017-06-14  4:01 ` [PATCH 07/10] ext4: add support for passing in stream information for buffered writes Jens Axboe
2017-06-14  4:01 ` [PATCH 08/10] xfs: " Jens Axboe
2017-06-14  4:01 ` Jens Axboe [this message]
2017-06-14  4:01 ` [PATCH 10/10] nvme: add support for streams and directives Jens Axboe
2017-06-14  4:10   ` Andreas Dilger
2017-06-14 15:45 ` [PATCHSET v2] Add support for write life time hints Martin K. Petersen
2017-06-14 15:53   ` Jens Axboe
2017-06-14 16:00     ` Martin K. Petersen
2017-06-14 16:03       ` Jens Axboe
2017-06-14 16:01     ` Christoph Hellwig
2017-06-14 16:02       ` Jens Axboe
2017-06-14 16:04       ` Martin K. Petersen
2017-06-14 16:26         ` Jens Axboe
2017-06-14 17:22         ` Jens Axboe
2017-06-14 23:39         ` Andreas Dilger
2017-06-15  3:26           ` Jens Axboe
2017-06-15  3:53             ` Andreas Dilger
2017-06-15  3:57               ` Jens Axboe
2017-06-15  4:38                 ` Jens Axboe
2017-06-16 13:58             ` Christoph Hellwig
2017-06-16 14:40               ` Jens Axboe
2017-06-16 15:52                 ` Christoph Hellwig
2017-06-16 15:55                   ` Jens Axboe

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=1497412919-19400-10-git-send-email-axboe@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=adilger@dilger.ca \
    --cc=linux-block@vger.kernel.org \
    --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).