From: scott.bauer@intel.com (Scott Bauer)
Subject: [PATCH] nvme: Implement NS Optimial IO Boundary from 1.3 Spec
Date: Fri, 12 May 2017 14:29:05 -0600 [thread overview]
Message-ID: <1494620945-8061-1-git-send-email-scott.bauer@intel.com> (raw)
The NVMe 1.3 spec introduces Namespace Optimal IO Boundaries (NOIOB).
This feature standardizes the stripe mechanism we currently have quirks for.
This patch implements the necessary logic to handle this new feature.
Signed-off-by: Scott Bauer <scott.bauer at intel.com>
---
drivers/nvme/host/core.c | 7 +++++++
include/linux/nvme.h | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index d5e0906..69d2798 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -1000,6 +1000,7 @@ static void __nvme_revalidate_disk(struct gendisk *disk, struct nvme_id_ns *id)
u8 lbaf, pi_type;
u16 old_ms;
unsigned short bs;
+ unsigned int iob;
old_ms = ns->ms;
lbaf = id->flbas & NVME_NS_FLBAS_LBA_MASK;
@@ -1027,6 +1028,12 @@ static void __nvme_revalidate_disk(struct gendisk *disk, struct nvme_id_ns *id)
ns->pi_type = pi_type;
blk_queue_logical_block_size(ns->queue, bs);
+ if (ns->ctrl->vs >= NVME_VS(1, 3, 0) && le16_to_cpu(id->noiob)) {
+ /* Convert from controller logical blocks to 512 sectors. */
+ iob = ((unsigned int)le16_to_cpu(id->noiob)) << (ns->lba_shift - 9);
+ if (is_power_of_2(iob))
+ blk_queue_chunk_sectors(ns->queue, iob);
+ }
if (ns->ms && !blk_get_integrity(disk) && !ns->ext)
nvme_init_integrity(ns);
diff --git a/include/linux/nvme.h b/include/linux/nvme.h
index b625bac..d19b193 100644
--- a/include/linux/nvme.h
+++ b/include/linux/nvme.h
@@ -274,7 +274,7 @@ struct nvme_id_ns {
__le16 nabsn;
__le16 nabo;
__le16 nabspf;
- __u16 rsvd46;
+ __le16 noiob;
__u8 nvmcap[16];
__u8 rsvd64[40];
__u8 nguid[16];
--
2.7.4
next reply other threads:[~2017-05-12 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 20:29 Scott Bauer [this message]
2017-05-12 21:18 ` [PATCH] nvme: Implement NS Optimial IO Boundary from 1.3 Spec Keith Busch
2017-05-15 15:01 ` Christoph Hellwig
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=1494620945-8061-1-git-send-email-scott.bauer@intel.com \
--to=scott.bauer@intel.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