Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 2147D2F12BB for ; Thu, 26 Feb 2026 09:44:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772099061; cv=none; b=cLbpjAI4CuK5mS7n+vIOwLZ4XGWvS6WiKhVaEs2xoiAwhHhbTLkQavfvkCFSVR+Bp/Wc4kDl2eVQpTrhj0RJ2+iPXTIwaGtQquz1QhSqxi2neyO5Wcgsa/kManRo9BVztXMcfiKO3cuYqanGq11bD0sT6LeDFHFma4LezLE4mIs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772099061; c=relaxed/simple; bh=arEp4p3Lz0gsbfUSGfe1BI/JlbjVGOC5vG4aqJm7jeE=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=eDi57MVdNOnjJyxkPn5SuyOSaaUS6dLfZF1/4Q+HcwwuAAlWQsgHjr27a7Rf3Vv2BCgGIIjI31PrMB2uWK1xkRnZzQi7AusvNPuEd7JRwjEFnSH+Nl2NcppQ209kClsxrdbpQui7Sokiybk7f6VTx98acueIPH7lY4b/VG0lplY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=m8QaLT8E; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="m8QaLT8E" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CE024C19422; Thu, 26 Feb 2026 09:44:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772099060; bh=arEp4p3Lz0gsbfUSGfe1BI/JlbjVGOC5vG4aqJm7jeE=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=m8QaLT8EvXJEXqSvD/oC+3ZjA769sea/RsDrQVZZxH7RtqH66belgFnGC0c4YJ18Y elD128DjhswOq5ncD8unOfFY22StoLnpL+m5hCUE8y3HMrWZkxbeGBmfR7meZiWHaY nywwq65lrlw8hKlm0gZkBzptca9u/tcP5to1R+96N1noPYMiaVbMrbILmsTKw5VxeJ 6ywvWoWddoI/Cg/jLp7EStV//Yg+0XDGLeULZ93mjoCwbQUxcXIVrWMFjeB/WH9Zyb vDnWh2cmeYj7iQsGbC6DtXA+Uoj+m+4waQCaSTUrGxC65IZ53YHWNR1sp2oDbUU0El 1haS+QFj/P5Cw== Message-ID: <4919267aa2f6471005e24282f85348b2af7689ec.camel@kernel.org> Subject: Re: [LSF/MM/BPF TOPIC] NVMe over MPTCP: Multi-Fold Acceleration for NVMe over TCP in Multi-NIC Environments From: Geliang Tang To: Ming Lei Cc: lsf-pc@lists.linux-foundation.org, linux-nvme@lists.infradead.org, mptcp@lists.linux.dev, Matthieu Baerts , Mat Martineau , Paolo Abeni , Hannes Reinecke Date: Thu, 26 Feb 2026 17:44:14 +0800 In-Reply-To: References: X-Priority: 1 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.58.2 (3.58.2-1.fc43) Precedence: bulk X-Mailing-List: mptcp@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Hi Ming, On Wed, 2026-02-25 at 13:57 +0800, Ming Lei wrote: > Hi Geliang, > > Looks one interesting topic! Thanks for your reply. > > On Thu, Jan 29, 2026 at 12:13:25PM +0800, Geliang Tang wrote: > > As one of the MPTCP upstream developers, I'm recently working on > > adding > > MPTCP support to 'NVMe over TCP'. This approach achieves a multi- > > fold > > performance improvement over using standard TCP. The implementation > > and > > testing phases are largely complete. The code is currently in the > > RFC > > stage and has undergone several rounds of discussion and iteration > > on > > the MPTCP mailing list [1]. It will be sent to the NVMe mailing > > list > > shortly. > > > > 1. Introduction to MPTCP > > > > Multipath TCP (MPTCP), standardized in RFC 8684, represents a major > > evolution of the TCP protocol. It enables a single transport > > connection > > to utilize multiple network paths simultaneously, providing > > benefits in > > redundancy, resilience, and bandwidth aggregation. Since its > > introduction in Linux kernel v5.6, it has become a key technology > > for > > modern networking, particularly in multi-NIC environments. > > > > On a supported system such as Linux, an MPTCP socket is created by > > specifying the IPPROTO_MPTCP protocol in the socket() system call: > > > > int fd = socket(AF_INET, SOCK_STREAM, IPPROTO_MPTCP); > > > > This creates a socket that appears as a standard TCP socket to the > > application but uses the MPTCP protocol stack underneath. > > > > For more details, please visit the project website: > > https://mptcp.dev. > > > > 2. Implementation > > > > 'NVMe over TCP' establishes multiple TCP connections between the > > target > > and host for data transfer. This includes one admin queue > > connection > > for management traffic and multiple I/O queue connections for data > > traffic, with the number typically scaling with available CPU > > cores. > > While these multiple TCP connections (using the same IP address but > > different ports) help distribute computational load across CPUs, > > all > > data traffic still flows through a single network interface card > > (NIC), > > even in multi-NIC environments. > > > > The 'NVMe over MPTCP' solution enhances 'NVMe over TCP' by > > replacing > > the multiple TCP connections with multiple MPTCP connections, > > leaving > > other mechanisms unchanged. Internally, each MPTCP connection can > > establish multiple subflows based on the number of configured NICs. > > This distributes data traffic across all available NICs, thereby > > increasing aggregate transmission speed. > > NVMe supports multipath, which can apply load balance or sort of > algorithm > to maximize network link/bandwidth too. > > Maybe you can compare mptcp with multipath in this viewpoint. Indeed worth comparing. Although they work at different layers, their goals share similarities. I'll compare them in a follow-up and get back to you. Thanks, -Geliang > > > > Thanks, > Ming >