From: Christoph Hellwig <hch@lst.de>
To: Surabhi Gogte <sgogte@purestorage.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
mkhalfella@purestorage.com, randyj@purestorage.com
Subject: Re: [PATCH v2] nvme-rdma: parallelize I/O queue allocation and startup
Date: Wed, 10 Jun 2026 14:04:58 +0200 [thread overview]
Message-ID: <20260610120458.GD19624@lst.de> (raw)
In-Reply-To: <20260604195321.2232838-1-sgogte@purestorage.com>
On Thu, Jun 04, 2026 at 01:53:21PM -0600, Surabhi Gogte wrote:
> +static void nvme_rdma_setup_queue_async(void *setup_queue, async_cookie_t cookie)
Overly long line. Easily fixed by renaming setup_queue to data
as in the async_schedule_domain prototype.
> +static int nvme_rdma_setup_io_queues(struct nvme_rdma_ctrl *ctrl, int first,
> + int last, size_t queue_size)
should first and last be unsigned?
Also please use two-tab indents for prototype continuations.
> + async_synchronize_full_domain(&setup_queue_domain);
>
> -out_free_queues:
> - for (i--; i >= 1; i--)
> - nvme_rdma_free_queue(&ctrl->queues[i]);
> + ret = atomic_read(&ctrl->qsetup_err);
> + if (ret) {
Jump to an error label if there was an error to reduce indentation
a bit below.
> + ctrl->queues[0].ctrl = ctrl;
> + ctrl->queues[0].queue_size = NVME_AQ_DEPTH;
> + error = nvme_rdma_alloc_queue(&ctrl->queues[0]);
The nvme_rdma_alloc_queue prototype change would be a nice prep patch
to split out from the main change.
prev parent reply other threads:[~2026-06-10 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 19:53 [PATCH v2] nvme-rdma: parallelize I/O queue allocation and startup Surabhi Gogte
2026-06-09 20:07 ` Keith Busch
2026-06-10 12:04 ` Christoph Hellwig [this message]
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=20260610120458.GD19624@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mkhalfella@purestorage.com \
--cc=randyj@purestorage.com \
--cc=sagi@grimberg.me \
--cc=sgogte@purestorage.com \
/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