[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230929102726.2985188-22-john.g.garry@oracle.com>
Date: Fri, 29 Sep 2023 10:27:26 +0000
From: John Garry <john.g.garry@...cle.com>
To: axboe@...nel.dk, kbusch@...nel.org, hch@....de, sagi@...mberg.me,
jejb@...ux.ibm.com, martin.petersen@...cle.com, djwong@...nel.org,
viro@...iv.linux.org.uk, brauner@...nel.org,
chandan.babu@...cle.com, dchinner@...hat.com
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, tytso@....edu, jbongio@...gle.com,
linux-api@...r.kernel.org, Alan Adamson <alan.adamson@...cle.com>,
John Garry <john.g.garry@...cle.com>
Subject: [PATCH 21/21] nvme: Support atomic writes
From: Alan Adamson <alan.adamson@...cle.com>
Support reading atomic write registers to fill in request_queue
properties.
Use following method to calculate limits:
atomic_write_max_bytes = flp2(NAWUPF ?: AWUPF)
atomic_write_unit_min = logical_block_size
atomic_write_unit_max = flp2(NAWUPF ?: AWUPF)
atomic_write_boundary = NABSPF
Signed-off-by: Alan Adamson <alan.adamson@...cle.com>
Signed-off-by: John Garry <john.g.garry@...cle.com>
---
drivers/nvme/host/core.c | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 21783aa2ee8e..aa0daacf4d7c 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -1926,6 +1926,35 @@ static void nvme_update_disk_info(struct gendisk *disk,
blk_queue_io_min(disk->queue, phys_bs);
blk_queue_io_opt(disk->queue, io_opt);
+ atomic_bs = rounddown_pow_of_two(atomic_bs);
+ if (id->nsfeat & NVME_NS_FEAT_ATOMICS && id->nawupf) {
+ if (id->nabo) {
+ dev_err(ns->ctrl->device, "Support atomic NABO=%x\n",
+ id->nabo);
+ } else {
+ u32 boundary = 0;
+
+ if (le16_to_cpu(id->nabspf))
+ boundary = (le16_to_cpu(id->nabspf) + 1) * bs;
+
+ if (is_power_of_2(boundary) || !boundary) {
+ blk_queue_atomic_write_max_bytes(disk->queue, atomic_bs);
+ blk_queue_atomic_write_unit_min_sectors(disk->queue, 1);
+ blk_queue_atomic_write_unit_max_sectors(disk->queue,
+ atomic_bs / bs);
+ blk_queue_atomic_write_boundary_bytes(disk->queue, boundary);
+ } else {
+ dev_err(ns->ctrl->device, "Unsupported atomic boundary=0x%x\n",
+ boundary);
+ }
+ }
+ } else if (ns->ctrl->subsys->awupf) {
+ blk_queue_atomic_write_max_bytes(disk->queue, atomic_bs);
+ blk_queue_atomic_write_unit_min_sectors(disk->queue, 1);
+ blk_queue_atomic_write_unit_max_sectors(disk->queue, atomic_bs / bs);
+ blk_queue_atomic_write_boundary_bytes(disk->queue, 0);
+ }
+
/*
* Register a metadata profile for PI, or the plain non-integrity NVMe
* metadata masquerading as Type 0 if supported, otherwise reject block
--
2.31.1
Powered by blists - more mailing lists