From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3E02C3B5306 for ; Mon, 6 Jul 2026 18:56:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783364195; cv=none; b=eG6pciOe7TrUBYQOJqO+e5mzMOmh1Xt2EnanQ7q3rolxMkHrr+uI3ZmWE/CocxfZzmWWBY36f8vgECtVNiSiG9JfYCsfqPi4rt1W62qEaDw+ixddsap1h10+unZ1A6CA/UVg5ACusAc38kLnCD4lcHFnHTJQ980LLqMEHhFlLmQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783364195; c=relaxed/simple; bh=q4zluGVeKdD4Rc/Sqmk60Q7TxGgIc5ir2G9jBeTb0LI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ZhbYct5JXUQlHFoVeIO/n71kgSSVB/L5rcoeKIlK3I/Omtwe7ZBW9Fr5JQxeJpGfObqa0oOIcR97hh99wbPyijMH+0ChZJAnzz7ZnqQyr8eF2htsRmjScySHklw5EG9fwjCGA4Kd4itGVqcGVUoMN1fb9Ge9jfHYGmjQu/LBI8Y= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=hgtx63Rf; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="hgtx63Rf" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 921601F000E9; Mon, 6 Jul 2026 18:56:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783364193; bh=q4zluGVeKdD4Rc/Sqmk60Q7TxGgIc5ir2G9jBeTb0LI=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=hgtx63RfWAQ8Ja1qDXSR75yrN4PWDRSFz9QF0MJFFHuW8Yc0gQZbAT+LwkoaB0hJJ tmo4t2G8ZDwnnChxkEbXk2Qg9K4nRMLScOs+gNByw/oDBwU+y5qtUpJafasgKyggcY n4wlJOZ3q9jQmr2IuB23aaqlCFDHxESDwlWGOjQN7g3X6q3Kvv8NWwgPLlNAWIEV3/ wHR/1VQDrMCGVWaut9G9tWXFoTs8fWRBaBEXL2dQVply9fl4o+SzYCK3IqlJg0i/zL aGqiK8Tm/gyk+yPkfXSIL+b5OXorjARoeJtsQ7vHQVSQYgStxyNS7l6s+LfYtw8BJW S3ajH6qI2yktQ== Date: Mon, 6 Jul 2026 12:56:32 -0600 From: Keith Busch To: Surabhi Gogte Cc: Christoph Hellwig , Jens Axboe , Sagi Grimberg , 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 Message-ID: References: <20260627041551.1981256-1-sgogte@purestorage.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260627041551.1981256-1-sgogte@purestorage.com> On Fri, Jun 26, 2026 at 10:15:49PM -0600, 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. Thanks, applied to nvme-7.3.