git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Small patch to add support for MPTCP on Linux

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
May 17, 2025, 13:39 UTC
Message-ID
<a76dda61-f60c-4221-83db-5e165a2478b1@gmail.com>
In-Reply-To
<4YPEWS.J5JRNETKLXF1@unrealasia.net>
On 17/05/2025 14:10, Muhammad Nuzaihan wrote:
Show 9 quoted lines
>> 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.

Show 7 quoted lines
> 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.

Show 7 quoted lines
>> 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

Previous: Muhammad NuzaihanNext: Junio C Hamano
Message 6 of 14 in “Small patch to add support for MPTCP on Linux”
  1. Muhammad NuzaihanMay 16, 2025
  2. brian m. carlsonMay 16, 2025
  3. Muhammad NuzaihanMay 17, 2025
  4. brian m. carlsonMay 17, 2025
  5. Muhammad NuzaihanMay 17, 2025
  6. Phillip WoodMay 17, 2025
  7. Junio C HamanoMay 19, 2025
  8. Muhammad NuzaihanMay 20, 2025
  9. Matthieu BaertsMay 20, 2025
  10. Junio C HamanoMay 20, 2025
  11. Matthieu BaertsMay 20, 2025
  12. Junio C HamanoMay 20, 2025
  13. Matthieu BaertsMay 22, 2025
  14. Muhammad NuzaihanMay 17, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.