From: Joel Granados <joel.granados@kernel.org>
To: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Joel Granados <joel.granados@kernel.org>
Subject: [PATCH RFC v2 11/14] nvme: Implement CDQ traversal on the read path
Date: Fri, 24 Jul 2026 13:11:05 +0200 [thread overview]
Message-ID: <20260724-jag-cdq-lkml-v2-11-659a7449e849@kernel.org> (raw)
In-Reply-To: <20260724-jag-cdq-lkml-v2-0-659a7449e849@kernel.org>
Replace the initial -EOPNOTSUPP stub with a call to
nvme_traversecopy_cdq which copies new controller entries to the user
space buffer, forwards and wraps host_head around when it reaches the
end of the queue.
Signed-off-by: Joel Granados <joel.granados@kernel.org>
---
drivers/nvme/host/cdq.c | 73 +++++++++++++++++++++++++++++++++++++++++++++++--
drivers/nvme/host/cdq.h | 7 +++++
2 files changed, 78 insertions(+), 2 deletions(-)
diff --git a/drivers/nvme/host/cdq.c b/drivers/nvme/host/cdq.c
index 7fe08afa0d80db5f3d60993aba05624b5c59b309..36107cf2fe11ff212d5b02dd5513fe02e3ae8f81 100644
--- a/drivers/nvme/host/cdq.c
+++ b/drivers/nvme/host/cdq.c
@@ -5,6 +5,7 @@
#include <linux/anon_inodes.h>
#include <linux/file.h>
+#include <linux/uaccess.h>
#include "nvme.h"
#include "cdq.h"
@@ -169,6 +170,75 @@ static inline void nvme_release_cdq_backing(struct cdq_nvme_queue *cdq)
nvme_free_cdqmem_chunks(cdq);
}
+
+static inline void *nvme_get_cdq_entryvaddr(struct cdq_nvme_queue *cdq,
+ unsigned int entry_idx)
+{
+ return cdq->chunks[entry_idx / NVME_CDQ_MQ_ENTRY_PER_CHUNK].vaddr +
+ (entry_idx % NVME_CDQ_MQ_ENTRY_PER_CHUNK) * NVME_CDQ_MQ_ENTRY_NRBYTES;
+}
+
+/* Advance cdq->host_head at most nrbytes and return actual advanced bytes */
+static size_t nvme_advance_cdq(struct cdq_nvme_queue *cdq, size_t max_nrbyte)
+{
+ size_t target_nbyte = 0;
+ void *entry;
+ u8 phase_bit;
+ u32 cdq_nrentry = cdq->size_nbyte / NVME_CDQ_MQ_ENTRY_NRBYTES;
+
+ while (target_nbyte < max_nrbyte) {
+ entry = nvme_get_cdq_entryvaddr(cdq, cdq->host_head);
+ phase_bit = (*(u8 *)(entry + NVME_CDQ_MQ_PHASE_OFFSET) & NVME_CDQ_MQ_PHASE_MASK);
+
+ if (phase_bit == cdq->phase_bit)
+ break;
+
+ cdq->host_head = (cdq->host_head + 1) % cdq_nrentry;
+ target_nbyte += NVME_CDQ_MQ_ENTRY_NRBYTES;
+ if (unlikely(cdq->host_head == 0))
+ cdq->phase_bit = ~cdq->phase_bit & NVME_CDQ_MQ_PHASE_MASK;
+ }
+
+ return target_nbyte;
+}
+
+static ssize_t nvme_traversecopy_cdq(struct cdq_nvme_queue *cdq, size_t max_nrbyte,
+ void *priv_data)
+{
+ char __user *to_buf = priv_data;
+ void *from_buf;
+ u32 init_host_head = cdq->host_head;
+ u8 init_phase_bit = cdq->phase_bit;
+
+ size_t target_nbyte = nvme_advance_cdq(cdq, max_nrbyte);
+ size_t copied_nbyte = 0, chunks_idx, entry_idx, tx_nbytes;
+
+ if (target_nbyte == 0)
+ goto out;
+
+ for (chunks_idx = init_host_head / NVME_CDQ_MQ_ENTRY_PER_CHUNK,
+ entry_idx = init_host_head % NVME_CDQ_MQ_ENTRY_PER_CHUNK;
+ copied_nbyte < target_nbyte;
+ chunks_idx = (chunks_idx + 1) % cdq->nr_chunks, entry_idx = 0) {
+ from_buf = cdq->chunks[chunks_idx].vaddr +
+ (entry_idx * NVME_CDQ_MQ_ENTRY_NRBYTES);
+ tx_nbytes = min(target_nbyte - copied_nbyte,
+ NVME_CDQ_CHUNK_SIZE - (entry_idx * NVME_CDQ_MQ_ENTRY_NRBYTES));
+ if (copy_to_user(to_buf, from_buf, tx_nbytes))
+ goto err_out;
+ copied_nbyte += tx_nbytes;
+ to_buf += tx_nbytes;
+ }
+
+out:
+ return copied_nbyte;
+
+err_out:
+ cdq->host_head = init_host_head;
+ cdq->phase_bit = init_phase_bit;
+ return -EFAULT;
+}
+
static ssize_t nvme_cdq_fops_read(struct file *filep, char __user *buf,
size_t size_nbyte, loff_t *ppos)
{
@@ -187,8 +257,7 @@ static ssize_t nvme_cdq_fops_read(struct file *filep, char __user *buf,
if (!READ_ONCE(cdq->valid_mem))
return -EINVAL;
- /* CDQ traversal not implemented yet. */
- return -EOPNOTSUPP;
+ return nvme_traversecopy_cdq(cdq, nbytes, buf);
}
/* File reference already dropped by the close path, so don't fput() */
diff --git a/drivers/nvme/host/cdq.h b/drivers/nvme/host/cdq.h
index a8c714ab5fada4325463013c2ffb23a117cd8423..96f208264c6144d26aa4ffc34854bb16d3f19af9 100644
--- a/drivers/nvme/host/cdq.h
+++ b/drivers/nvme/host/cdq.h
@@ -9,6 +9,8 @@
#include "nvme.h"
#define NVME_CDQ_MQ_ENTRY_NRBYTES 32
+#define NVME_CDQ_MQ_PHASE_MASK 0x1
+#define NVME_CDQ_MQ_PHASE_OFFSET (NVME_CDQ_MQ_ENTRY_NRBYTES - 1)
/*
* The CDQ backing is a set of coherent DMA chunks expressed in
@@ -17,6 +19,7 @@
#define NVME_CDQ_CHUNK_ORDER 2
#define NVME_CDQ_CHUNK_SIZE (PAGE_SIZE << NVME_CDQ_CHUNK_ORDER)
#define NVME_CDQ_PAGES_PER_CHUNK (NVME_CDQ_CHUNK_SIZE / NVME_CTRL_PAGE_SIZE)
+#define NVME_CDQ_MQ_ENTRY_PER_CHUNK (NVME_CDQ_CHUNK_SIZE / NVME_CDQ_MQ_ENTRY_NRBYTES)
/* Max PRP List pages we are willing to chain to describe a discontiguous CDQ. */
#define MAX_NR_CDQ_PRPS 20
@@ -45,6 +48,10 @@ struct cdq_nvme_queue {
/* True if mem for chunks and prps is valid */
bool valid_mem;
+ /* How far the CDQ was consumed by the host */
+ u32 host_head;
+ u8 phase_bit;
+
/* Manage refs for read FD and controller xarray */
struct kref ref;
};
--
2.50.1
next prev parent reply other threads:[~2026-07-24 11:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 11:10 [PATCH RFC v2 00/14] nvme: Controller Data Queue (CDQ) support Joel Granados
2026-07-24 11:10 ` [PATCH RFC v2 01/14] nvme: Add NVME_AER_ONE_SHOT callback handler Joel Granados
2026-07-24 11:10 ` [PATCH RFC v2 02/14] nvme: Add NVMe Controller Data Queue command Joel Granados
2026-07-24 11:10 ` [PATCH RFC v2 03/14] nvme: Add track send command Joel Granados
2026-07-24 11:10 ` [PATCH RFC v2 04/14] nvme: Add CDQ to xarray and define delete path Joel Granados
2026-07-24 11:10 ` [PATCH RFC v2 05/14] nvme: Allocate CDQ backing memory from coherent DMA chunks Joel Granados
2026-07-24 11:11 ` [PATCH RFC v2 06/14] nvme: Add file descriptor to read CDQs Joel Granados
2026-07-24 11:11 ` [PATCH RFC v2 07/14] nvme: Add the create CDQ functionality Joel Granados
2026-07-24 11:11 ` [PATCH RFC v2 08/14] nvme: Submit track send command to start/stop the CDQ Joel Granados
2026-07-24 11:11 ` [PATCH RFC v2 09/14] nvme: Coordinate CDQ backing mem and CDQ FD Joel Granados
2026-07-24 11:11 ` [PATCH RFC v2 10/14] nvme: Pin a ctrl ref to every CDQ Joel Granados
2026-07-24 11:11 ` Joel Granados [this message]
2026-07-24 11:11 ` [PATCH RFC v2 12/14] nvme: Update the controller with the CDQ set-feature cmd Joel Granados
2026-07-24 11:11 ` [PATCH RFC v2 13/14] nvme: Use eventfd for CDQ Tail pointer triggers Joel Granados
2026-07-24 11:11 ` [PATCH RFC v2 14/14] nvme: Add NVME_IOCTL_CDQ to create/delete migration CDQs Joel Granados
2026-07-29 23:48 ` [PATCH RFC v2 00/14] nvme: Controller Data Queue (CDQ) support Chaitanya Kulkarni
2026-08-03 12:38 ` Joel Granados
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=20260724-jag-cdq-lkml-v2-11-659a7449e849@kernel.org \
--to=joel.granados@kernel.org \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®