From: Finn Thain <fthain@telegraphics.com.au>
To: Keith Busch <kbusch@kernel.org>
Cc: Tim Walker <tim.t.walker@seagate.com>,
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: Tue, 11 Feb 2020 09:25:59 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.22.394.2002110914510.9@nippy.intranet> (raw)
In-Reply-To: <20200210204313.GA3736@dhcp-10-100-145-180.wdl.wdc.com>
On Mon, 10 Feb 2020, Keith Busch wrote:
> Right now the nvme driver unconditionally sets QUEUE_FLAG_NONROT
> (non-rational, i.e. ssd), on all nvme namespace's request_queue flags.
I agree -- the standard nomenclature is not rational ;-) Air-cooled is not
"solid state". Any round-robin algorithm is "rotational". No expensive
array is a "R.A.I.D.". There's no "S.C.S.I." on a large system...
next prev parent reply other threads:[~2020-02-10 22:26 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
2020-02-10 22:25 ` Finn Thain [this message]
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=alpine.LNX.2.22.394.2002110914510.9@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=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).