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>
Cc: Klaus Jensen <k.jensen@samsung.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Joel Granados <joel.granados@kernel.org>
Subject: [PATCH RFC 4/8] nvme: Add function to create a CDQ
Date: Mon, 14 Jul 2025 11:15:35 +0200 [thread overview]
Message-ID: <20250714-jag-cdq-v1-4-01e027d256d5@kernel.org> (raw)
In-Reply-To: <20250714-jag-cdq-v1-0-01e027d256d5@kernel.org>
On CDQ initialization:
* The memory holding the CDQ structure (struct cdq_nvme_queue) is
allocated,
* DMAable memory for the entries is allocated.
* A CDQ create command is sent to the controller
* The newly created CDQ is stored in ctrl->cdqs
* A CDQ file descriptor is created
* The CDQ id returned by the controller and the file descriptor value
are returned to the user
Signed-off-by: Joel Granados <joel.granados@kernel.org>
---
drivers/nvme/host/core.c | 116 +++++++++++++++++++++++++++++++++++++++++++++++
drivers/nvme/host/nvme.h | 4 ++
2 files changed, 120 insertions(+)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 8517253002941e1f892e62bb7dacac40395b16d9..81b7183a4e3167290e68dc2eb26a8dbcd88c7924 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -1319,6 +1319,122 @@ static const struct file_operations cdq_fops = {
.read = nvme_cdq_fops_read,
};
+static int nvme_cdq_fd(struct cdq_nvme_queue *cdq, int *fdno)
+{
+ int ret = 0;
+ struct file *filep;
+
+ *fdno = -1;
+
+ if (cdq->filep)
+ return -EINVAL;
+
+ filep = anon_inode_getfile("[cdq-readfd]", &cdq_fops, cdq, O_RDWR);
+ if (IS_ERR(filep)) {
+ ret = PTR_ERR(filep);
+ goto out;
+ }
+
+ *fdno = get_unused_fd_flags(O_CLOEXEC | O_RDONLY | O_DIRECT);
+ if (*fdno < 0) {
+ ret = *fdno;
+ goto out_fput;
+ }
+
+ fd_install(*fdno, filep);
+ cdq->filep = filep;
+
+ return 0;
+
+out_fput:
+ put_unused_fd(*fdno);
+ fput(filep);
+out:
+ return ret;
+}
+
+static int nvme_cdq_alloc(struct nvme_ctrl *ctrl, struct cdq_nvme_queue **cdq,
+ u32 entry_nr, u32 entry_nbyte)
+{
+ struct cdq_nvme_queue *ret_cdq = kzalloc(sizeof(*ret_cdq), GFP_KERNEL);
+
+ if (!ret_cdq)
+ return -ENOMEM;
+
+ ret_cdq->entries = dma_alloc_coherent(ctrl->dev,
+ entry_nr * entry_nbyte,
+ &ret_cdq->entries_dma_addr,
+ GFP_KERNEL);
+ if (!ret_cdq->entries) {
+ kfree(ret_cdq);
+ return -ENOMEM;
+ }
+
+ *cdq = ret_cdq;
+
+ return 0;
+}
+
+static void nvme_cdq_free(struct nvme_ctrl *ctrl, struct cdq_nvme_queue *cdq)
+{
+ dma_free_coherent(ctrl->dev, cdq->entry_nr * cdq->entry_nbyte,
+ cdq->entries, cdq->entries_dma_addr);
+ kfree(cdq);
+}
+
+
+int nvme_cdq_create(struct nvme_ctrl *ctrl, struct nvme_command *c,
+ const u32 entry_nr, const u32 entry_nbyte,
+ uint cdqp_offset, uint cdqp_mask,
+ u16 *cdq_id, int *cdq_fd)
+{
+ int ret, fdno;
+ struct cdq_nvme_queue *cdq, *xa_ret;
+ union nvme_result result = { };
+
+ ret = nvme_cdq_alloc(ctrl, &cdq, entry_nr, entry_nbyte);
+ if (ret)
+ return ret;
+ c->cdq.prp1 = cdq->entries_dma_addr;
+
+ ret = __nvme_submit_sync_cmd(ctrl->admin_q, c, &result, NULL, 0, NVME_QID_ANY, 0);
+ if (ret)
+ goto err_cdq_free;
+
+ cdq->cdq_id = le16_to_cpu(result.u16);
+ cdq->entry_nbyte = entry_nbyte;
+ cdq->entry_nr = entry_nr;
+ cdq->ctrl = ctrl;
+ cdq->cdqp_offset = cdqp_offset;
+ cdq->cdqp_mask = cdqp_mask;
+
+ xa_ret = xa_store(&ctrl->cdqs, cdq->cdq_id, cdq, GFP_KERNEL);
+ if (xa_is_err(xa_ret)) {
+ ret = xa_err(xa_ret);
+ goto err_cdq_free;
+ }
+
+ ret = nvme_cdq_fd(cdq, &fdno);
+ if (ret)
+ goto err_cdq_erase;
+
+ *cdq_id = cdq->cdq_id;
+ *cdq_fd = fdno;
+
+ return 0;
+
+err_cdq_erase:
+ xa_erase(&ctrl->cdqs, cdq->cdq_id);
+
+err_cdq_free:
+ cdq_id = NULL;
+ cdq_fd = NULL;
+ nvme_cdq_free(ctrl, cdq);
+
+ return ret;
+}
+EXPORT_SYMBOL_GPL(nvme_cdq_create);
+
void nvme_passthru_end(struct nvme_ctrl *ctrl, struct nvme_ns *ns, u32 effects,
struct nvme_command *cmd, int status)
{
diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
index 800970a0bb87f7a3b6e855f56a2493a7deed1ecd..ddec5b44fe022831280458ed9fc1cb1ed11633b7 100644
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -1207,6 +1207,10 @@ u32 nvme_passthru_start(struct nvme_ctrl *ctrl, struct nvme_ns *ns, u8 opcode);
int nvme_execute_rq(struct request *rq, bool at_head);
void nvme_passthru_end(struct nvme_ctrl *ctrl, struct nvme_ns *ns, u32 effects,
struct nvme_command *cmd, int status);
+int nvme_cdq_create(struct nvme_ctrl *ctrl, struct nvme_command *c,
+ const u32 entry_nr, const u32 entry_nbyte,
+ uint cdqp_offset, uint cdqp_mask,
+ u16 *cdq_id, int *cdq_fd);
struct nvme_ctrl *nvme_ctrl_from_file(struct file *file);
struct nvme_ns *nvme_find_get_ns(struct nvme_ctrl *ctrl, unsigned nsid);
bool nvme_get_ns(struct nvme_ns *ns);
--
2.47.2
next prev parent reply other threads:[~2025-07-14 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 9:15 [PATCH RFC 0/8] nvme: Add Controller Data Queue to the nvme driver Joel Granados
2025-07-14 9:15 ` [PATCH RFC 1/8] nvme: Add CDQ command definitions for contiguous PRPs Joel Granados
2025-07-14 9:15 ` [PATCH RFC 2/8] nvme: Add cdq data structure to nvme_ctrl Joel Granados
2025-07-14 9:15 ` [PATCH RFC 3/8] nvme: Add file descriptor to read CDQs Joel Granados
2025-07-14 9:15 ` Joel Granados [this message]
2025-07-14 9:15 ` [PATCH RFC 5/8] nvme: Add function to delete CDQ Joel Granados
2025-07-14 9:15 ` [PATCH RFC 6/8] nvme: Add a release ops to cdq file ops Joel Granados
2025-07-14 9:15 ` [PATCH RFC 7/8] nvme: Add Controller Data Queue (CDQ) ioctl command Joel Granados
2025-07-14 9:15 ` [PATCH RFC 8/8] nvme: Connect CDQ ioctl to nvme driver Joel Granados
2025-07-14 13:02 ` [PATCH RFC 0/8] nvme: Add Controller Data Queue to the " Christoph Hellwig
2025-07-18 11:33 ` Joel Granados
2025-07-21 6:26 ` Christoph Hellwig
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=20250714-jag-cdq-v1-4-01e027d256d5@kernel.org \
--to=joel.granados@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=k.jensen@samsung.com \
--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®