Skip to content

Commit 1029298

Browse files
calebsanderkeithbusch
authored andcommitted
nvme: set discard_granularity from NPDG/NPDA
Currently, nvme_config_discard() always sets the discard_granularity queue limit to the logical block size. However, NVMe namespaces can advertise a larger preferred discard granularity in the NPDG or NPDA field of the Identify Namespace structure or the NPDGL or NPDAL fields of the I/O Command Set Specific Identify Namespace structure. Use these fields to compute the discard_granularity limit. The logic is somewhat involved. First, the fields are optional. NPDG is only reported if the low bit of OPTPERF is set in NSFEAT. NPDA is reported if any bit of OPTPERF is set. And NPDGL and NPDAL are reported if the high bit of OPTPERF is set. NPDGL and NPDAL can also each be set to 0 to opt out of reporting a limit. I/O Command Set Specific Identify Namespace may also not be supported by older NVMe controllers. Another complication is that multiple values may be reported among NPDG, NPDGL, NPDA, and NPDAL. The spec says to prefer the values reported in the L variants. The spec says NPDG should be a multiple of NPDA and NPDGL should be a multiple of NPDAL, but it doesn't specify a relationship between NPDG and NPDAL or NPDGL and NPDA. So use the maximum of the reported NPDG(L) and NPDA(L) values as the discard_granularity. Signed-off-by: Caleb Sander Mateos <[email protected]> Signed-off-by: Keith Busch <[email protected]>
1 parent b465046 commit 1029298

1 file changed

Lines changed: 32 additions & 3 deletions

File tree

drivers/nvme/host/core.c

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2059,12 +2059,13 @@ static void nvme_set_ctrl_limits(struct nvme_ctrl *ctrl,
20592059
}
20602060

20612061
static bool nvme_update_disk_info(struct nvme_ns *ns, struct nvme_id_ns *id,
2062-
struct queue_limits *lim)
2062+
struct nvme_id_ns_nvm *nvm, struct queue_limits *lim)
20632063
{
20642064
struct nvme_ns_head *head = ns->head;
20652065
struct nvme_ctrl *ctrl = ns->ctrl;
20662066
u32 bs = 1U << head->lba_shift;
20672067
u32 atomic_bs, phys_bs, io_opt = 0;
2068+
u32 npdg = 1, npda = 1;
20682069
bool valid = true;
20692070
u8 optperf;
20702071

@@ -2117,7 +2118,35 @@ static bool nvme_update_disk_info(struct nvme_ns *ns, struct nvme_id_ns *id,
21172118
else
21182119
lim->max_hw_discard_sectors = 0;
21192120

2120-
lim->discard_granularity = lim->logical_block_size;
2121+
/*
2122+
* NVMe namespaces advertise both a preferred deallocate granularity
2123+
* (for a discard length) and alignment (for a discard starting offset).
2124+
* However, Linux block devices advertise a single discard_granularity.
2125+
* From NVM Command Set specification 1.1 section 5.2.2, the NPDGL/NPDAL
2126+
* fields in the NVM Command Set Specific Identify Namespace structure
2127+
* are preferred to NPDG/NPDA in the Identify Namespace structure since
2128+
* they can represent larger values. However, NPDGL or NPDAL may be 0 if
2129+
* unsupported. NPDG and NPDA are 0's based.
2130+
* From Figure 115 of NVM Command Set specification 1.1, NPDGL and NPDAL
2131+
* are supported if the high bit of OPTPERF is set. NPDG is supported if
2132+
* the low bit of OPTPERF is set. NPDA is supported if either is set.
2133+
* NPDG should be a multiple of NPDA, and likewise NPDGL should be a
2134+
* multiple of NPDAL, but the spec doesn't say anything about NPDG vs.
2135+
* NPDAL or NPDGL vs. NPDA. So compute the maximum instead of assuming
2136+
* NPDG(L) is the larger. If neither NPDG, NPDGL, NPDA, nor NPDAL are
2137+
* supported, default the discard_granularity to the logical block size.
2138+
*/
2139+
if (optperf & 0x2 && nvm && nvm->npdgl)
2140+
npdg = le32_to_cpu(nvm->npdgl);
2141+
else if (optperf & 0x1)
2142+
npdg = from0based(id->npdg);
2143+
if (optperf & 0x2 && nvm && nvm->npdal)
2144+
npda = le32_to_cpu(nvm->npdal);
2145+
else if (optperf)
2146+
npda = from0based(id->npda);
2147+
if (check_mul_overflow(max(npdg, npda), lim->logical_block_size,
2148+
&lim->discard_granularity))
2149+
lim->discard_granularity = lim->logical_block_size;
21212150

21222151
if (ctrl->dmrl)
21232152
lim->max_discard_segments = ctrl->dmrl;
@@ -2384,7 +2413,7 @@ static int nvme_update_ns_info_block(struct nvme_ns *ns,
23842413
nvme_set_ctrl_limits(ns->ctrl, &lim, false);
23852414
nvme_configure_metadata(ns->ctrl, ns->head, id, nvm, info);
23862415
nvme_set_chunk_sectors(ns, id, &lim);
2387-
if (!nvme_update_disk_info(ns, id, &lim))
2416+
if (!nvme_update_disk_info(ns, id, nvm, &lim))
23882417
capacity = 0;
23892418

23902419
if (IS_ENABLED(CONFIG_BLK_DEV_ZONED) &&

0 commit comments

Comments
 (0)