Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH 9/9] nvme: add support for streams and directives
Date: Tue, 27 Jun 2017 08:56:34 -0600	[thread overview]
Message-ID: <b9bd5753-453d-0952-b4a7-cddd4715b933@kernel.dk> (raw)
In-Reply-To: <cd3cc640-5eb2-aeaf-a3a9-904436faae77@kernel.dk>

On 06/27/2017 08:46 AM, Jens Axboe wrote:
> On 06/27/2017 08:44 AM, Christoph Hellwig wrote:
>> On Tue, Jun 27, 2017@08:16:49AM -0600, Jens Axboe wrote:
>>> But we have to handle it, not doing so would be fragile. So our
>>> options are:
>>>
>>> 1) Keep the stream_mappings[] array. It's simple, and it'll work
>>>    for any number of streams.
>>>
>>> 2) Kill stream_mappings[] and just do the MOD again.
>>
>> 3) print a message and tell streams aren't supported on this device.
> 
> Is that your nvme preference - if less than 4 streams, just ignore it?
> Would seem a shame to lose out with 2 streams, I can think of several
> hot/cold scenarios that would probably work fine with that. But at the
> same time, not a big deal to me, if you prefer just turning it off
> for < 4 streams, that's fine with me.

http://git.kernel.dk/cgit/linux-block/commit/?h=write-stream&id=98335ae1347a9a08adc831e77e8fefcf06ab8282

-- 
Jens Axboe

  reply	other threads:[~2017-06-27 14:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  0:21 [PATCHSET v9] Add support for write life time hints Jens Axboe
2017-06-21  0:21 ` [PATCH 1/9] fs: add fcntl() interface for setting/getting " Jens Axboe
2017-06-26  9:51   ` Christoph Hellwig
2017-06-26 13:55     ` Jens Axboe
2017-06-26 16:09       ` Darrick J. Wong
2017-06-26 16:29         ` Jens Axboe
2017-06-21  0:21 ` [PATCH 2/9] block: add support for write hints in a bio Jens Axboe
2017-06-26  9:52   ` Christoph Hellwig
2017-06-21  0:22 ` [PATCH 3/9] blk-mq: expose stream write hints through debugfs Jens Axboe
2017-06-26  9:52   ` Christoph Hellwig
2017-06-21  0:22 ` [PATCH 4/9] fs: add O_DIRECT support for sending down write life time hints Jens Axboe
2017-06-26  9:55   ` Christoph Hellwig
2017-06-26 14:12     ` Jens Axboe
2017-06-21  0:22 ` [PATCH 5/9] fs: add support for buffered writeback to pass down write hints Jens Axboe
2017-06-21  0:22 ` [PATCH 6/9] ext4: add support for passing in write hints for buffered writes Jens Axboe
2017-06-21  0:22 ` [PATCH 7/9] xfs: " Jens Axboe
2017-06-21  1:35   ` Darrick J. Wong
2017-06-21  1:46     ` Jens Axboe
2017-06-26  9:56   ` Christoph Hellwig
2017-06-26 14:16     ` Jens Axboe
2017-06-21  0:22 ` [PATCH 8/9] btrfs: " Jens Axboe
2017-06-21  0:22 ` [PATCH 9/9] nvme: add support for streams and directives Jens Axboe
2017-06-26  9:59   ` Christoph Hellwig
2017-06-26 13:56     ` Jens Axboe
2017-06-26 19:36       ` Andreas Dilger
2017-06-26 19:39         ` Jens Axboe
2017-06-27 14:11       ` Christoph Hellwig
2017-06-27 14:16         ` Jens Axboe
2017-06-27 14:44           ` Christoph Hellwig
2017-06-27 14:46             ` Jens Axboe
2017-06-27 14:56               ` Jens Axboe [this message]
2017-06-26 17:52     ` Martin K. Petersen
2017-06-26 18:00       ` Jens Axboe
2017-06-21  1:30 ` [PATCHSET v9] Add support for write life time hints Martin K. Petersen
2017-06-21  1:45   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2017-06-19 17:04 [PATCHSET v8] " Jens Axboe
2017-06-19 17:05 ` [PATCH 9/9] nvme: add support for streams and directives 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=b9bd5753-453d-0952-b4a7-cddd4715b933@kernel.dk \
    --to=axboe@kernel.dk \
    /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