From: Sagi Grimberg <sagi@grimberg.me>
To: Surabhi Gogte <sgogte@purestorage.com>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@kernel.dk>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
mkhalfella@purestorage.com, randyj@purestorage.com,
adailey@purestorage.com
Subject: Re: [PATCH v4 0/2] nvme-rdma: parallelize I/O queue setup
Date: Sun, 23 Aug 2026 04:10:17 +0300 [thread overview]
Message-ID: <55310833-fd75-4d0f-b910-0a19090c2e9c@grimberg.me> (raw)
In-Reply-To: <20260627041551.1981256-1-sgogte@purestorage.com>
On 27/06/2026 7:15, Surabhi Gogte wrote:
> This patch series parallelizes nvme-rdma connection and reconnection by
> setting up I/O queues in parallel instead of sequentially. Allocation and
> startup of each queue are combined into a single per-queue async work
> item, so per-queue connection latency overlaps across all queues. This
> matters most on high-core-count hosts with many I/O queues, where serial
> setup dominates connect time.
>
> Patch 1 is a preparatory refactor: nvme_rdma_alloc_queue() takes a queue
> pointer so allocation and startup can be folded into a single async
> worker.
>
> Patch 2 contains the implementation for async setup of I/O queues.
>
> Testing on a 64-core host with 64 I/O queues shows nvme-rdma connection
> time reduced from ~1.4s to 416ms.
>
> Signed-off-by: Surabhi Gogte <sgogte@purestorage.com>
Would it be possible to do the same for nvme-tcp?
prev parent reply other threads:[~2026-08-23 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 4:15 Surabhi Gogte
2026-06-27 4:15 ` [PATCH v4 1/2] nvme-rdma: refactor nvme_rdma_alloc_queue() to take a queue pointer Surabhi Gogte
2026-06-27 4:15 ` [PATCH v4 2/2] nvme-rdma: parallelize I/O queue allocation and startup Surabhi Gogte
2026-06-29 12:34 ` Christoph Hellwig
2026-07-06 18:56 ` [PATCH v4 0/2] nvme-rdma: parallelize I/O queue setup Keith Busch
2026-08-23 1:10 ` Sagi Grimberg [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=55310833-fd75-4d0f-b910-0a19090c2e9c@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
all inboxes | Powered by JetHome®