From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andreas Dilger <adilger@dilger.ca>,
Martin Petersen <martin.petersen@oracle.com>,
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 09:55:11 -0600 [thread overview]
Message-ID: <cedaf1bd-70ca-c48e-aacb-7569901c3aab@kernel.dk> (raw)
In-Reply-To: <20170616155246.GC27209@infradead.org>
On 06/16/2017 09:52 AM, Christoph Hellwig wrote:
> On Fri, Jun 16, 2017 at 08:40:11AM -0600, Jens Axboe wrote:
>> On 06/16/2017 07:58 AM, Christoph Hellwig wrote:
>>>> >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?
>>
>> Yep, it's on Mark Callaghan's github:
>>
>> https://github.com/mdcallag/rocksdb
>>
>> This is using mostly the v1 I posted, the only difference is that I just
>> named the four flags RWF_S[1-4].
>
> That commits look a bit like mess, but I guess I shouldn't expect
> kernel-style changelogs and patch separation on github :)
It's just a quick test patch, not intended to be pushed upstream in its
current state. But it's good enough to validate it for testing. In summary,
what the patch does is:
- Redo log, level 0 and 1 of the LSM goes to stream 1.
- Level 2 goes to stream 2
- Level 3 goes to stream 3
- Level 4 and above goes to stream 4.
Each level is roughly 10x in size, but written at the same rate. So each
level roughly has a life time 10x of data writes of the previous one.
--
Jens Axboe
prev parent reply other threads:[~2017-06-16 15:55 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
2017-06-16 14:40 ` Jens Axboe
2017-06-16 15:52 ` Christoph Hellwig
2017-06-16 15:55 ` Jens Axboe [this message]
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=cedaf1bd-70ca-c48e-aacb-7569901c3aab@kernel.dk \
--to=axboe@kernel.dk \
--cc=adilger@dilger.ca \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.