From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Andreas Dilger <adilger@dilger.ca>,
Martin Petersen <martin.petersen@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
fsdevel <linux-fsdevel@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: [PATCHSET v2] Add support for write life time hints
Date: Fri, 16 Jun 2017 06:58:03 -0700 [thread overview]
Message-ID: <20170616135803.GA808@infradead.org> (raw)
In-Reply-To: <9e152ed7-ed49-bb62-902c-0daac7646a86@kernel.dk>
> >From my perspective, all I really care about is the 4 hints. It's a
> simple enough interface that applications can understand and use it, and
> we don't need any management of actual stream IDs. I think that has the
> highest chance of success. Modifying an application to use it is
> trivial, even something like RocksDB (if you havehad to make changes
> to RocksDB, you'll get this).
Btw, are your current RocksDB patches available somewhere?
next prev parent reply other threads:[~2017-06-16 13:58 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 ` [PATCH 09/10] btrfs: " Jens Axboe
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 [this message]
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=20170616135803.GA808@infradead.org \
--to=hch@infradead.org \
--cc=adilger@dilger.ca \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin.petersen@oracle.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).