From: Sagi Grimberg <sagi@grimberg.me>
To: Surabhi Gogte <sgogte@purestorage.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
mkhalfella@purestorage.com, randyj@purestorage.com,
adailey@purestorage.com
Subject: Re: [PATCH v2 1/2] nvme-tcp: refactor I/O queue setup path
Date: Mon, 31 Aug 2026 00:56:39 +0300 [thread overview]
Message-ID: <d55e8223-44cb-42e7-bb41-d659f206d573@grimberg.me> (raw)
In-Reply-To: <20260824225648.316962-2-sgogte@purestorage.com>
On 25/08/2026 1:56, 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_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 5fda9661bdb7..354668ad29ac 100644
> --- a/drivers/nvme/host/tcp.c
> +++ b/drivers/nvme/host/tcp.c
> @@ -2171,10 +2171,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) {
> /*
> @@ -2196,6 +2194,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);
> @@ -2212,7 +2217,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_io_queue_count(struct nvme_ctrl *ctrl)
Strange function name... maybe nvme_tcp_set_io_queue_count?
next prev parent reply other threads:[~2026-08-30 21:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 22:56 [PATCH v2 0/2] nvme-tcp: parallelize I/O queue connect Surabhi Gogte
2026-08-24 22:56 ` [PATCH v2 1/2] nvme-tcp: refactor I/O queue setup path Surabhi Gogte
2026-08-30 21:56 ` Sagi Grimberg [this message]
2026-09-02 21:25 ` Surabhi Gogte (she/her)
2026-08-24 22:56 ` [PATCH v2 2/2] nvme-tcp: parallelize I/O queue allocation and startup Surabhi Gogte
2026-08-24 23:58 ` Randy Jennings
2026-08-30 22:00 ` Sagi Grimberg
2026-08-30 22:25 ` Mohamed Khalfella
2026-08-30 22:44 ` Sagi Grimberg
2026-08-30 22:59 ` Mohamed Khalfella
2026-09-04 16:04 ` Surabhi Gogte (she/her)
2026-09-05 22:29 ` Sagi Grimberg
2026-09-04 16:05 ` Surabhi Gogte (she/her)
2026-09-05 22:30 ` Sagi Grimberg
2026-09-10 20:32 ` Surabhi Gogte (she/her)
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=d55e8223-44cb-42e7-bb41-d659f206d573@grimberg.me \
--to=sagi@grimberg.me \
--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=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