From: Jens Axboe <axboe@fb.com>
To: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Cc: <adilger@dilger.ca>, <david@fromorbit.com>, Jens Axboe <axboe@fb.com>
Subject: [PATCH 3/7] direct-io: add support for write stream IDs
Date: Tue, 5 May 2015 14:02:57 -0600 [thread overview]
Message-ID: <1430856181-19568-4-git-send-email-axboe@fb.com> (raw)
In-Reply-To: <1430856181-19568-1-git-send-email-axboe@fb.com>
Get the streamid from the file, if any, and set it on the bio.
Signed-off-by: Jens Axboe <axboe@fb.com>
---
fs/direct-io.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/direct-io.c b/fs/direct-io.c
index 745d2342651a..9acd6724889d 100644
--- a/fs/direct-io.c
+++ b/fs/direct-io.c
@@ -76,6 +76,7 @@ struct dio_submit {
int reap_counter; /* rate limit reaping */
sector_t final_block_in_request;/* doesn't change */
int boundary; /* prev block is at a boundary */
+ int streamid; /* Write stream ID */
get_block_t *get_block; /* block mapping function */
dio_submit_t *submit_io; /* IO submition function */
@@ -373,6 +374,8 @@ dio_bio_alloc(struct dio *dio, struct dio_submit *sdio,
sdio->bio = bio;
sdio->logical_offset_in_bio = sdio->cur_page_fs_offset;
+
+ bio_set_streamid(bio, sdio->streamid);
}
/*
@@ -1204,6 +1207,7 @@ do_blockdev_direct_IO(struct kiocb *iocb, struct inode *inode,
sdio.blkbits = blkbits;
sdio.blkfactor = i_blkbits - blkbits;
sdio.block_in_file = offset >> blkbits;
+ sdio.streamid = file_streamid(iocb->ki_filp);
sdio.get_block = get_block;
dio->end_io = end_io;
--
2.4.0.rc2.1.g3d6bc9a
next prev parent reply other threads:[~2015-05-05 20:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 20:02 [PATCH v2] Support for write stream IDs Jens Axboe
2015-05-05 20:02 ` [PATCH 1/7] block: add support for carrying a stream ID in a bio Jens Axboe
2015-05-05 20:02 ` [PATCH 2/7] Add support for per-file/inode stream ID Jens Axboe
2015-05-05 20:09 ` Christoph Hellwig
2015-05-05 20:02 ` Jens Axboe [this message]
2015-05-05 20:02 ` [PATCH 4/7] Add stream ID support for buffered mpage/__block_write_full_page() Jens Axboe
2015-05-05 20:02 ` [PATCH 5/7] btrfs: add support for write stream IDs Jens Axboe
2015-05-05 20:03 ` [PATCH 6/7] xfs: add support for buffered writeback stream ID Jens Axboe
2015-05-05 20:03 ` [PATCH 7/7] ext4: add support for write stream IDs Jens Axboe
2015-05-05 20:07 ` [PATCH v2] Support " Christoph Hellwig
2015-05-05 20:12 ` Jens Axboe
2015-05-05 20:20 ` Christoph Hellwig
2015-05-05 20:31 ` Jens Axboe
2015-05-05 20:43 ` Christoph Hellwig
2015-05-05 20:50 ` Christoph Hellwig
2015-05-05 20:51 ` Jeff Moyer
2015-05-05 21:05 ` Jens Axboe
2015-05-05 21:39 ` Martin K. Petersen
2015-05-05 21:48 ` Jens Axboe
2015-05-05 22:09 ` Martin K. Petersen
2015-05-06 14:26 ` Peter Zijlstra
2015-05-06 17:25 ` Jens Axboe
2015-05-06 16:50 ` Boaz Harrosh
2015-05-06 17:21 ` Jens Axboe
2015-05-07 19:19 ` Martin K. Petersen
2015-05-08 18:48 ` Jens Axboe
2015-05-12 2:50 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2015-04-18 20:03 Jens Axboe
2015-04-18 20:03 ` [PATCH 3/7] direct-io: add support " Jens Axboe
2015-03-25 15:07 [PATCH RFC v2] Support " Jens Axboe
2015-03-25 15:07 ` [PATCH 3/7] direct-io: add support " 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=1430856181-19568-4-git-send-email-axboe@fb.com \
--to=axboe@fb.com \
--cc=adilger@dilger.ca \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).