From: Jens Axboe <axboe@fb.com>
To: <axboe@kernel.dk>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Cc: <ming.l@ssi.samsung.com>, <adilger@dilger.c>, <david@fromorbit.com>
Subject: [PATCH v2] Support for write stream IDs
Date: Sat, 18 Apr 2015 14:03:02 -0600 [thread overview]
Message-ID: <1429387389-17029-1-git-send-email-axboe@fb.com> (raw)
Hi,
v2 of this posting. Changes since v1:
- Rebased on top of current master.
- Fix EINVAL -> -EINVAL typo.
- Cleanup up BIO_STREAM_OFFSET definition.
- Pack i_streamid and f_streamid better into struct file and struct
inode.
- Add a separate per-file hint, FADV_FILE_STREAMID. This only sets
the write stream on the file, not the inode. FADV_STREAMID sets
the hint both in the file and the inode.
block/bio.c | 2 ++
block/blk-core.c | 3 +++
fs/btrfs/extent_io.c | 1 +
fs/btrfs/inode.c | 1 +
fs/buffer.c | 4 ++--
fs/direct-io.c | 4 ++++
fs/ext4/page-io.c | 1 +
fs/inode.c | 1 +
fs/mpage.c | 1 +
fs/open.c | 1 +
fs/xfs/xfs_aops.c | 1 +
include/linux/blk_types.h | 28 +++++++++++++++++++++++++++-
include/linux/fs.h | 22 ++++++++++++++++++++++
include/uapi/linux/fadvise.h | 3 +++
mm/fadvise.c | 25 +++++++++++++++++++++++++
15 files changed, 95 insertions(+), 3 deletions(-)
next reply other threads:[~2015-04-18 20:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 20:03 Jens Axboe [this message]
2015-04-18 20:03 ` [PATCH 1/7] block: add support for carrying a stream ID in a bio Jens Axboe
2015-04-18 20:03 ` [PATCH 2/7] Add support for per-file/inode stream ID Jens Axboe
2015-04-18 20:03 ` [PATCH 3/7] direct-io: add support for write stream IDs Jens Axboe
2015-04-18 20:03 ` [PATCH 4/7] Add stream ID support for buffered mpage/__block_write_full_page() Jens Axboe
2015-04-18 20:03 ` [PATCH 5/7] btrfs: add support for write stream IDs Jens Axboe
2015-04-18 20:03 ` [PATCH 6/7] xfs: add support for buffered writeback stream ID Jens Axboe
2015-04-18 20:03 ` [PATCH 7/7] ext4: add support for write stream IDs Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2015-05-05 20:02 [PATCH v2] Support " Jens Axboe
2015-05-05 20:07 ` 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
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=1429387389-17029-1-git-send-email-axboe@fb.com \
--to=axboe@fb.com \
--cc=adilger@dilger.c \
--cc=axboe@kernel.dk \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.l@ssi.samsung.com \
/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).