From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v2 0/3] Add MPTCP support to Java Networking API
Date: Thu, 28 Aug 2025 11:57:44 +0200 [thread overview]
Message-ID: <3a401acb-bcc6-4885-a1a4-7aa88ed55cb5@kernel.org> (raw)
In-Reply-To: <cover.1756369940.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 28/08/2025 10:47, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v2:
> - drop redundant helpers as Matt suggested.
> - squash into fewer patches.
> - use "JNI_TRUE" and "(void)mptcp" in Java_sun_nio_ch_Net_socket0 as
> Xiang Gao suggested.
>
> The Multipath TCP (MPTCP) protocol (v1 / RFC 8684) has been added in
> the upstream Linux kernel since v5.6. See https://mptcp.dev.
>
> This patch series introduces comprehensive Multipath TCP (MPTCP)
> support to the Java Networking API, enabling applications to leverage
> MPTCP's capabilities for improved reliability and throughput.
Thank you for the new version! Feel free to start the process to
upstream these patches [1]. Don't hesitate to share here the link to the
new ticket.
[1] https://openjdk.org/guide/#i-have-a-patch-what-do-i-do
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-08-28 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 8:47 [PATCH mptcp-next v2 0/3] Add MPTCP support to Java Networking API Geliang Tang
2025-08-28 8:47 ` [PATCH mptcp-next v2 1/3] Add native MPTCP socket creation support Geliang Tang
2025-08-28 8:47 ` [PATCH mptcp-next v2 2/3] Add MPTCP support to Java Socket/ServerSocket APIs Geliang Tang
2025-08-28 8:47 ` [PATCH mptcp-next v2 3/3] Add test cases for MPTCP socket functionality Geliang Tang
2025-08-28 9:57 ` Matthieu Baerts [this message]
2025-09-03 6:16 ` [PATCH mptcp-next v2 0/3] Add MPTCP support to Java Networking API Geliang Tang
2025-09-03 10:49 ` 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=3a401acb-bcc6-4885-a1a4-7aa88ed55cb5@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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