git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Muhammad Nuzaihan <zaihan@unrealasia.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "phillip.wood" <phillip.wood@dunelm.org.uk>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: PATCH v2 [1/1]: MPTCP support for Git on Linux
Date: Sun, 18 May 2025 03:25:16 +0800	[thread overview]
Message-ID: <4A7FWS.KARM6LOQBQ5S3@unrealasia.net> (raw)
In-Reply-To: <xmqq5xhzqdmz.fsf@gitster.g>

Hi Junio,

MPTCP has been in development for 15 years and only reached maturity
in v1 of the protocol.

Only recently in 2020 that this protocol (v1) was officially merged
into the Linux kernel mainline but before that Linux MPTCP was developed
out-of-tree.

Apple had been using MPTCP in production for the
past 12 years for their iOS[1] for Apple's cloud services.

It's no longer an experimental technology it's in the IETF standards 
track[2]
and no longer in experimental track.

I know it's cumbersome to implement MPTCP for every application out 
there,
the same with IPv6 which already had been around for more than 20 years 
and still
not that widely adopted, especially for enterprises.

But i think we have to start somewhere. I myself had been working on 
IPv6
since 2003 and i think the late Jun Ichiro Hagino probably did the 
right thing
even though people around him might think otherwise.

Anyway, back to git. I think it will benefit the server side more with
aggregation but i started to work on this after realising how bad my 
hotel's wifi
and i have a WWAN module and thought of aggregating my bandwidth.

Since Go is enabled MPTCP by default in 1.24, it makes sense
for me to add more MPTCP support, at least on the Linux side of things. 
Go
is really popular not just web services but also load balancers (which 
can
also be TCP load balancers).

I cannot vouch Linux kernel's MPTCP implementation as someone had 
mentioned
about the CVE because of backpressure but that CVE was in 2022, 3 years 
ago.

Go 1.24 with MPTCP by default is only released this year, so time will 
tell. :-)

I think eventually just like IPv6, people will have knowledge on how it
works.

[1]http://blog.multipath-tcp.org/blog/html/2018/12/15/apple_and_multipath_tcp.html
[2]https://datatracker.ietf.org/doc/html/rfc8684

Regards,
Zaihan

On Sat, May 17 2025 at 11:46:12 AM -0700, Junio C Hamano 
<gitster@pobox.com> wrote:
> Muhammad Nuzaihan <zaihan@unrealasia.net> writes:
> 
>>  Hi,
>> 
>>  This patch is about Multi-Path TCP.
> 
> Perhaps reading and following Documentation/SubmittingPatches and
> possibly MyFirstContribution is in order.
> 
> How widely is MPTCP adopted?  I somehow feel that it is a losing
> proposition to _require_ that each and every _application_ to be
> updated to support it, but say if we take a random set of widely
> used application, how much of them have specific knowledge of how
> to work with MPTCP these days?
> 
> 
> 



      reply	other threads:[~2025-05-17 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17 17:02 PATCH v2 [1/1]: MPTCP support for Git on Linux Muhammad Nuzaihan
2025-05-17 18:30 ` PATCH v3 " Muhammad Nuzaihan
2025-05-17 18:46 ` PATCH v2 " Junio C Hamano
2025-05-17 19:25   ` Muhammad Nuzaihan [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=4A7FWS.KARM6LOQBQ5S3@unrealasia.net \
    --to=zaihan@unrealasia.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=sandals@crustytoothpaste.net \
    /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;
as well as URLs for NNTP newsgroup(s).