From: Hannes Reinecke <hare@suse.de>
To: Surabhi Gogte <sgogte@purestorage.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: Solganik Alexander <sashas@lightbitslabs.com>,
Roy Shterman <roys@lightbitslabs.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
mkhalfella@purestorage.com, randyj@purestorage.com,
adailey@purestorage.com
Subject: Re: [PATCH v3 2/3] nvme-tcp: refactor I/O queue setup path
Date: Mon, 21 Sep 2026 14:34:24 +0200 [thread overview]
Message-ID: <ead0bdd9-8f0f-4deb-ba1b-e078262c5164@suse.de> (raw)
In-Reply-To: <20260910202812.1642832-3-sgogte@purestorage.com>
On 9/10/26 10:28 PM, Surabhi Gogte wrote:
> Split the I/O queue setup helpers apart so that the individual steps can
> be called directly from nvme_tcp_configure_io_queues():
>
> - Queue count negotiation moves out of nvme_tcp_alloc_io_queues() into a
> new nvme_tcp_set_io_queue_count(), leaving the allocator with just the
> per-queue allocation loop.
> - TLS PSK validation moves out of __nvme_tcp_alloc_io_queues() into a
> new nvme_tcp_tls_check_psk().
> - nvme_tcp_configure_io_queues() now calls the three steps directly in
> the same order as before.
>
> Signed-off-by: Surabhi Gogte <sgogte@purestorage.com>
> ---
> drivers/nvme/host/tcp.c | 25 +++++++++++++++++++------
> 1 file changed, 19 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
> index 8e5e22febe2a..fe0e581608b4 100644
> --- a/drivers/nvme/host/tcp.c
> +++ b/drivers/nvme/host/tcp.c
> @@ -2172,10 +2172,8 @@ static int nvme_tcp_alloc_admin_queue(struct nvme_ctrl *ctrl)
> return ret;
> }
>
> -static int __nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl)
> +static int nvme_tcp_tls_check_psk(struct nvme_ctrl *ctrl)
> {
> - int i, ret;
> -
> if (nvme_tcp_tls_configured(ctrl)) {
> if (ctrl->opts->concat) {
> /*
> @@ -2197,6 +2195,13 @@ static int __nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl)
> }
> }
>
> + return 0;
> +}
> +
> +static int __nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl)
> +{
> + int i, ret;
> +
> for (i = 1; i < ctrl->queue_count; i++) {
> ret = nvme_tcp_alloc_queue(ctrl, i,
> ctrl->tls_pskid);
> @@ -2213,7 +2218,7 @@ static int __nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl)
> return ret;
> }
>
> -static int nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl)
> +static int nvme_tcp_set_io_queue_count(struct nvme_ctrl *ctrl)
> {
> unsigned int nr_io_queues;
> int ret;
We are not only set the queue count, but also allocating the queues
themselves. Why not keep the original name?
> @@ -2235,14 +2240,22 @@ static int nvme_tcp_alloc_io_queues(struct nvme_ctrl *ctrl)
>
> nvmf_set_io_queues(ctrl->opts, nr_io_queues,
> to_tcp_ctrl(ctrl)->io_queues);
> - return __nvme_tcp_alloc_io_queues(ctrl);
> + return 0;
> }
>
> static int nvme_tcp_configure_io_queues(struct nvme_ctrl *ctrl, bool new)
> {
> int ret, nr_queues;
>
> - ret = nvme_tcp_alloc_io_queues(ctrl);
> + ret = nvme_tcp_set_io_queue_count(ctrl);
> + if (ret)
> + return ret;
> +
> + ret = nvme_tcp_tls_check_psk(ctrl);
> + if (ret)
> + return ret;
> +
> + ret = __nvme_tcp_alloc_io_queues(ctrl);
> if (ret)
> return ret;
>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2026-09-21 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 20:28 [PATCH v3 0/3] nvme-tcp: parallelize I/O setup queue in connect Surabhi Gogte
2026-09-10 20:28 ` [PATCH v3 1/3] nvme-tcp: store and use the caller's network namespace Surabhi Gogte
2026-09-11 21:22 ` Sagi Grimberg
2026-09-21 12:32 ` Hannes Reinecke
2026-09-10 20:28 ` [PATCH v3 2/3] nvme-tcp: refactor I/O queue setup path Surabhi Gogte
2026-09-11 21:23 ` Sagi Grimberg
2026-09-21 12:34 ` Hannes Reinecke [this message]
2026-09-10 20:28 ` [PATCH v3 3/3] nvme-tcp: parallelize I/O queue allocation and startup Surabhi Gogte
2026-09-11 21:27 ` Sagi Grimberg
2026-09-22 19:54 ` Surabhi Gogte (she/her)
2026-09-21 12:37 ` Hannes Reinecke
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=ead0bdd9-8f0f-4deb-ba1b-e078262c5164@suse.de \
--to=hare@suse.de \
--cc=adailey@purestorage.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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=roys@lightbitslabs.com \
--cc=sagi@grimberg.me \
--cc=sashas@lightbitslabs.com \
--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
all inboxes | Powered by JetHome®