From: Keith Busch <kbusch@kernel.org>
To: Tim Walker <tim.t.walker@seagate.com>
Cc: linux-block@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [LSF/MM/BPF TOPIC] NVMe HDD
Date: Mon, 10 Feb 2020 12:43:13 -0800 [thread overview]
Message-ID: <20200210204313.GA3736@dhcp-10-100-145-180.wdl.wdc.com> (raw)
In-Reply-To: <CANo=J14resJ4U1nufoiDq+ULd0k-orRCsYah8Dve-y8uCjA62Q@mail.gmail.com>
On Mon, Feb 10, 2020 at 02:20:10PM -0500, Tim Walker wrote:
> -What Linux storage stack assumptions do we need to be aware of as we
> develop these devices with drastically different performance
> characteristics than traditional NAND? For example, what schedular or
> device driver level changes will be needed to integrate NVMe HDDs?
Right now the nvme driver unconditionally sets QUEUE_FLAG_NONROT
(non-rational, i.e. ssd), on all nvme namespace's request_queue flags. We
need the specification to define a capability bit or field associated
with the namespace to tell the driver otherwise, then we can propogate
that information up to the block layer.
Even without that, an otherwise spec compliant HDD should function as an
nvme device with existing software, but I would be interested to hear
additional ideas or feature gaps with other protocols that should be
considered in order to make an nvme hdd work well.
next prev parent reply other threads:[~2020-02-10 20:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 19:20 [LSF/MM/BPF TOPIC] NVMe HDD Tim Walker
2020-02-10 20:43 ` Keith Busch [this message]
2020-02-10 22:25 ` Finn Thain
2020-02-11 12:28 ` Ming Lei
2020-02-11 19:01 ` Tim Walker
2020-02-12 1:47 ` Damien Le Moal
2020-02-12 22:03 ` Ming Lei
2020-02-13 2:40 ` Damien Le Moal
2020-02-13 7:53 ` Ming Lei
2020-02-13 8:24 ` Damien Le Moal
2020-02-13 8:34 ` Ming Lei
2020-02-13 16:30 ` Keith Busch
2020-02-14 0:40 ` Ming Lei
2020-02-13 3:02 ` Martin K. Petersen
2020-02-13 3:12 ` Tim Walker
2020-02-13 4:17 ` Martin K. Petersen
2020-02-14 7:32 ` Hannes Reinecke
2020-02-14 14:40 ` Keith Busch
2020-02-14 16:04 ` Hannes Reinecke
2020-02-14 17:05 ` Keith Busch
2020-02-18 15:54 ` Tim Walker
2020-02-18 17:41 ` Keith Busch
2020-02-18 17:52 ` James Smart
2020-02-19 1:31 ` Ming Lei
2020-02-19 1:53 ` Damien Le Moal
2020-02-19 2:15 ` Ming Lei
2020-02-19 2:32 ` Damien Le Moal
2020-02-19 2:56 ` Tim Walker
2020-02-19 16:28 ` Tim Walker
2020-02-19 20:50 ` Keith Busch
2020-02-14 0:35 ` Ming Lei
2020-02-12 21:52 ` Ming Lei
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=20200210204313.GA3736@dhcp-10-100-145-180.wdl.wdc.com \
--to=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tim.t.walker@seagate.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).