nvme: implement non-mdts command limits
Keith Busch
maintainerPATCH v2 1/1 nvme: implement non-mdts command limits
Commands that access LBA contents without a data transfer between the host historically have not had a spec defined upper limit. The driver set the queue constraints for such commands to the max data transfer size just to be safe, but this artificial constraint frequently limits devices below their capabilities.
The NVMe Workgroup ratified TP4040 defines how a controller may advertise their non-MDTS limits. Use these if provided, and default to the current constraints if not. Since the Dataset Management command limits are defined in logical blocks, but without a namespace to tell us the logical block size, the code defaults to the safe 512b size.
---v1->v2:
Merge up with nvme-1.3
Fixed function name nvme_mps_size_to_sectors() (used to say bytes).
Reuse the nvme_mps_size_to_sectors() function for max_hw_sectors calculation.
drivers/nvme/host/core.c | 87 ++++++++++++++++++++++++++++++++-------- drivers/nvme/host/nvme.h | 3 ++ include/linux/nvme.h | 10 +++++ 3 files changed, 84 insertions(+), 16 deletions(-)
drivers/nvme/host/core.c +71 -16
@@ -1926,7 +1926,7 @@ static void nvme_config_discard(struct gendisk *disk, struct nvme_ns *ns)struct request_queue *queue = disk->queue;u32 size =queue_logical_block_size (queue); -if (!(ctrl->oncs &NVME_CTRL_ONCS_DSM )) { +if (ctrl->max_discard_sectors ==0 ) {blk_queue_flag_clear (QUEUE_FLAG_DISCARD , queue);return ; }
@@ -1944,25 +1944,17 @@ static void nvme_config_discard(struct gendisk *disk, struct nvme_ns *ns)if (blk_queue_flag_test_and_set (QUEUE_FLAG_DISCARD , queue))return ; -blk_queue_max_discard_sectors (queue,UINT_MAX ); -blk_queue_max_discard_segments (queue,NVME_DSM_MAX_RANGES ); +blk_queue_max_discard_sectors (queue, ctrl->max_discard_sectors); +blk_queue_max_discard_segments (queue, ctrl->max_discard_segments);if (ctrl->quirks &NVME_QUIRK_DEALLOCATE_ZEROES )blk_queue_max_write_zeroes_sectors (queue,UINT_MAX ); } -/* -* Even though NVMe spec explicitly states that MDTS is not applicable to the -* write-zeroes, we are cautious and limit the size to the controllers -* max_hw_sectors value, which is based on the MDTS field and possibly other -* limiting factors. -*/ static void nvme_config_write_zeroes (struct request_queue *q,struct nvme_ctrl *ctrl) { -if ((ctrl->oncs &NVME_CTRL_ONCS_WRITE_ZEROES ) && - !(ctrl->quirks &NVME_QUIRK_DISABLE_WRITE_ZEROES )) -blk_queue_max_write_zeroes_sectors (q, ctrl->max_hw_sectors); +blk_queue_max_write_zeroes_sectors (q, ctrl->max_zeroes_sectors); }static bool nvme_ns_ids_valid (struct nvme_ns_ids *ids)
@@ -3038,14 +3030,72 @@ static int nvme_get_effects_log(struct nvme_ctrl *ctrl, u8 csi,return 0 ; } +static inline u32 nvme_mps_size_to_sectors (struct nvme_ctrl *ctrl,u8 size) +{ +int page_shift =NVME_CAP_MPSMIN (ctrl->cap) +12 ; + +return 1 << (size + page_shift -9 ); +} + +static int nvme_init_non_mdts_limits (struct nvme_ctrl *ctrl) +{ +struct nvme_command c = { }; +struct nvme_id_ctrl_nvm *id; +int ret; + +if (!(ctrl->oncs &NVME_CTRL_ONCS_DSM )) { + ctrl->max_discard_sectors =0 ; + ctrl->max_discard_segments =0 ; + }else { + ctrl->max_discard_sectors =UINT_MAX ; + ctrl->max_discard_segments =NVME_DSM_MAX_RANGES ; + } + +/* +* Even though NVMe spec explicitly states that MDTS is not applicable +* to the write-zeroes, we are cautious and limit the size to the +* controllers max_hw_sectors value, which is based on the MDTS field +* and possibly other limiting factors. +*/ +if (!(ctrl->quirks &NVME_QUIRK_DISABLE_WRITE_ZEROES ) && + (ctrl->oncs &NVME_CTRL_ONCS_WRITE_ZEROES )) + ctrl->max_zeroes_sectors = ctrl->max_hw_sectors; +else + ctrl->max_zeroes_sectors =0 ; + +if (ctrl->vs <NVME_VS (1 ,2 ,0 )) +return 0 ; + + id =kzalloc (sizeof (*id),GFP_KERNEL ); +if (!id) +return 0 ; + + c.identify.opcode = nvme_admin_identify; + c.identify.cns =NVME_ID_CNS_CS_CTRL ; + c.identify.csi =NVME_CSI_NVM ; + + ret =nvme_submit_sync_cmd (ctrl->admin_q, &c, id,sizeof (*id)); +if (ret) + goto free_data; + +if (id->dmrl) + ctrl->max_discard_segments = id->dmrl; +if (id->dmrsl) + ctrl->max_discard_sectors =le32_to_cpu (id->dmrsl); +if (id->wzsl) + ctrl->max_zeroes_sectors =nvme_mps_size_to_sectors (ctrl, id->wzsl); + +free_data: +kfree (id); +return ret; +} +static int nvme_init_identify (struct nvme_ctrl *ctrl) {struct nvme_id_ctrl *id; -int ret, page_shift;u32 max_hw_sectors;bool prev_apst_enabled; - - page_shift =NVME_CAP_MPSMIN (ctrl->cap) +12 ; +int ret; ret =nvme_identify_ctrl (ctrl, &id);if (ret) {
@@ -3102,7 +3152,7 @@ static int nvme_init_identify(struct nvme_ctrl *ctrl)atomic_set (&ctrl->abort_limit, id->acl +1 ); ctrl->vwc = id->vwc;if (id->mdts) - max_hw_sectors =1 << (id->mdts + page_shift -9 ); + max_hw_sectors =nvme_mps_size_to_sectors (ctrl, id->mdts);else max_hw_sectors =UINT_MAX ; ctrl->max_hw_sectors =
@@ -3213,6 +3263,10 @@ int nvme_init_ctrl_finish(struct nvme_ctrl *ctrl)if (ret)return ret; + ret =nvme_init_non_mdts_limits (ctrl); +if (ret <0 ) +return ret; + ret =nvme_configure_apst (ctrl);if (ret <0 )return ret;
@@ -4743,6 +4797,7 @@ static inline void _nvme_check_size(void)BUILD_BUG_ON (sizeof (struct nvme_id_ns ) !=NVME_IDENTIFY_DATA_SIZE );BUILD_BUG_ON (sizeof (struct nvme_id_ns_zns ) !=NVME_IDENTIFY_DATA_SIZE );BUILD_BUG_ON (sizeof (struct nvme_id_ctrl_zns ) !=NVME_IDENTIFY_DATA_SIZE ); +BUILD_BUG_ON (sizeof (struct nvme_id_ctrl_nvm ) !=NVME_IDENTIFY_DATA_SIZE );BUILD_BUG_ON (sizeof (struct nvme_lba_range_type ) !=64 );BUILD_BUG_ON (sizeof (struct nvme_smart_log ) !=512 );BUILD_BUG_ON (sizeof (struct nvme_dbbuf ) !=64 );
drivers/nvme/host/nvme.h +3 -0
@@ -276,6 +276,9 @@ struct nvme_ctrl {u32 max_hw_sectors;u32 max_segments;u32 max_integrity_segments; +u32 max_discard_sectors; +u32 max_discard_segments; +u32 max_zeroes_sectors;#ifdef CONFIG_BLK_DEV_ZONED u32 max_zone_append;#endif
include/linux/nvme.h +10 -0
@@ -405,6 +405,16 @@ struct nvme_id_ctrl_zns {__u8 rsvd1[4095 ]; }; +struct nvme_id_ctrl_nvm { +__u8 vsl; +__u8 wzsl; +__u8 wusl; +__u8 dmrl; +__le32 dmrsl; +__le64 dmsl; +__u8 rsvd16[4080 ]; +}; +enum {NVME_ID_CNS_NS =0x00 ,NVME_ID_CNS_CTRL =0x01 ,
Signature · 7 lines
2.25.4 _______________________________________________ Linux-nvme mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-nvme
Christoph Hellwig
maintainerdrivers/nvme/host/core.c static void nvme_config_discard(struct gendisk *disk, struct nvme_ns *ns) · line 1957
Quoted 4 lines
static void nvme_config_write_zeroes(struct
request_queue*q,drivers/nvme/host/core.c +1
-0struct nvme_ctrl *ctrl) { +blk_queue_max_write_zeroes_sectors (q, ctrl->max_zeroes_sectors);
I think at this point we can kill nvme_config_write_zeroes :)
drivers/nvme/host/core.c static int nvme_get_effects_log(struct nvme_ctrl *ctrl, u8 csi, · line 3052
Quoted 13 lines
drivers/nvme/host/core.c +13
-0+static int nvme_init_non_mdts_limits (struct nvme_ctrl *ctrl) +{ +struct nvme_command c = { }; +struct nvme_id_ctrl_nvm *id; +int ret; + +if (!(ctrl->oncs &NVME_CTRL_ONCS_DSM )) { + ctrl->max_discard_sectors =0 ; + ctrl->max_discard_segments =0 ; + }else { + ctrl->max_discard_sectors =UINT_MAX ; + ctrl->max_discard_segments =NVME_DSM_MAX_RANGES ; + }
Can you switch the polarity here, that is avoid the pointless negation in the if?
Review
Quoted 2 lines
(quoted diff) +2
-0+ if (ctrl->vs < NVME_VS(1, 2, 0)) + return 0;
This check doesn't make much sense to me, as new TPs can always apply to older spec versions as well. Instead this probably should be a nvme_ctrl_limited_cns() check.
_______________________________________________
Linux-nvme mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-nvme