From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 0/2] NVMe 1.4 Identify Namespace Support
Date: Fri, 7 Jun 2019 18:44:19 +0200 [thread overview]
Message-ID: <20190607164419.GC7307@lst.de> (raw)
In-Reply-To: <CAOSXXT55eF5hUqoyyrY1OV1iPs3bKwU6FbmTN6m_-sr2JXQ5dg@mail.gmail.com>
On Fri, Jun 07, 2019@10:26:47AM -0600, Keith Busch wrote:
> The intention for this feature is to communicate potentially larger
> physical blocks than page sizes, so I was just hoping for enforcing
> that access from filesystems. Something like this from xfs
>
> https://lwn.net/Articles/770975/
>
> would be a nice feature.
No need for new NVMe features for that, you just need a controller
that exposes a LBA format with a data size larger than 4k, which has
been perfectly doable since NVMe 1.0.
prev parent reply other threads:[~2019-06-07 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 21:28 [PATCH 0/2] NVMe 1.4 Identify Namespace Support Bart Van Assche
2019-06-06 21:28 ` [PATCH 1/2] nvme: Introduce NVMe 1.4 Identify Namespace fields in struct nvme_id_ns Bart Van Assche
2019-06-06 21:40 ` Chaitanya Kulkarni
2019-06-07 15:18 ` Martin K. Petersen
2019-06-06 21:28 ` [PATCH 2/2] nvme: Set physical block size and optimal I/O size according to NVMe 1.4 Bart Van Assche
2019-06-06 21:42 ` Chaitanya Kulkarni
2019-06-06 21:48 ` Bart Van Assche
2019-06-06 21:58 ` Chaitanya Kulkarni
2019-06-07 16:42 ` Christoph Hellwig
2019-06-07 15:19 ` Martin K. Petersen
2019-06-07 16:42 ` Christoph Hellwig
2019-06-07 13:56 ` [PATCH 0/2] NVMe 1.4 Identify Namespace Support Keith Busch
2019-06-07 15:21 ` Martin K. Petersen
2019-06-07 16:26 ` Keith Busch
2019-06-07 16:44 ` Christoph Hellwig [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=20190607164419.GC7307@lst.de \
--to=hch@lst.de \
/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).