diff options
| author | Caleb Sander Mateos <csander@purestorage.com> | 2026-02-27 13:23:47 -0700 |
|---|---|---|
| committer | Keith Busch <kbusch@kernel.org> | 2026-03-27 07:35:04 -0700 |
| commit | 9110b85244f142ca4bcaea27be408c778d3c48d0 (patch) | |
| tree | f2626d5ca7e24252cbbf1a09a0fd3a7929f5be30 /tools/perf/scripts/python | |
| parent | ac61e869bef13a43d624893559acbac3a4e2a341 (diff) | |
nvme: fold nvme_config_discard() into nvme_update_disk_info()
The choice of what queue limits are set in nvme_update_disk_info() vs.
nvme_config_discard() seems a bit arbitrary. A subsequent commit will
compute the discard_granularity limit using struct nvme_id_ns, which is
only passed to nvme_update_disk_info() currently. So move the logic in
nvme_config_discard() to nvme_update_disk_info(). Replace several
instances of ns->ctrl in nvme_update_disk_info() with the ctrl variable
brought from nvme_config_discard().
Signed-off-by: Caleb Sander Mateos <csander@purestorage.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
