git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Muhammad Nuzaihan <zaihan@unrealasia.net>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: Small patch to add support for MPTCP on Linux
Date: Sat, 17 May 2025 14:39:38 +0100	[thread overview]
Message-ID: <a76dda61-f60c-4221-83db-5e165a2478b1@gmail.com> (raw)
In-Reply-To: <4YPEWS.J5JRNETKLXF1@unrealasia.net>

On 17/05/2025 14:10, Muhammad Nuzaihan wrote:
>> I want to point out that the kernel and libc headers used to compile a
>> binary need not reflect the actual code in the running kernel.  With the
>> advent of containers, people frequently run a different operating system
>> inside a container than they do outside a container and thus we need to
>> consider all of the possible combinations.
> 
> In that case, i'll add a check for the OS that git is built on with 
> "defined(__linux__)"
> if that helps.

As brian has already said I think it would be better to have a Makefile 
knob to control this which defaults to being on for linux. Take a look 
at the various USE_xxx definitions in the Makefile and config.mak.uname 
for setting default compile flags for different operating systems.

> Also another check if a socket is supported by looking for a return 
> value of
> "EAI_SOCKTYPE" (not EINVAL) and fallback to regular TCP if that is 
> returned.
> 
> EAI_SOCKTYPE should work across different UNIX systems as this is a 
> posix error code.

That error is not mentioned in the documentation for MCTCP on Linux [1]. 
Please make sure your code checks for the errno values described in the 
documentation.

>> On the Git list, we try not to assume that everyone has read all of the
>> technical documentation about a subject and instead we explain, at a
>> high level, how the change is and how it's supposed to work.  Your
>> commit message should convince me (and everyone else, especially Junio,
>> the maintainer) that your change is valuable and should be applied.
> 
> It's just a small trival amount of code but anyway.
That maybe so but please make sure that the commit message explains the 
reason for this change - what the advantages and disadvantages of using 
MPTCP are and what steps you have taken to make sure git continues to 
work on systems that do not support MPTCP.

Thanks

Phillip

[1] 
https://www.kernel.org/doc/html/next/networking/mptcp.html#creating-mptcp-sockets

  reply	other threads:[~2025-05-17 13:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 17:56 Small patch to add support for MPTCP on Linux Muhammad Nuzaihan
2025-05-16 20:33 ` brian m. carlson
2025-05-17  7:19   ` Muhammad Nuzaihan
     [not found]     ` <CAOYsWhkMb8hxjnYRTgAb269N=e-Vyw10Go5M=RA-8PyCjXPttA@mail.gmail.com>
2025-05-17  8:46       ` Muhammad Nuzaihan
2025-05-17 10:15     ` brian m. carlson
2025-05-17 13:10       ` Muhammad Nuzaihan
2025-05-17 13:39         ` Phillip Wood [this message]
2025-05-19 23:49           ` Junio C Hamano
2025-05-20  4:32             ` Muhammad Nuzaihan
2025-05-20 10:54             ` Matthieu Baerts
2025-05-20 15:44               ` Junio C Hamano
2025-05-20 20:34                 ` Matthieu Baerts
2025-05-20 22:02                   ` Junio C Hamano
2025-05-22 11:12                     ` Matthieu Baerts

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=a76dda61-f60c-4221-83db-5e165a2478b1@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=sandals@crustytoothpaste.net \
    --cc=zaihan@unrealasia.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).