From: Geliang Tang <geliang@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2 0/3] Add MPTCP support to Java Networking API
Date: Wed, 03 Sep 2025 14:16:09 +0800 [thread overview]
Message-ID: <2dc597d59d3aff65b2955f5accf0a14e2c788cf5.camel@kernel.org> (raw)
In-Reply-To: <3a401acb-bcc6-4885-a1a4-7aa88ed55cb5@kernel.org>
Hi Matt,
On Thu, 2025-08-28 at 11:57 +0200, Matthieu Baerts wrote:
> 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
>
I followed the instructions and "Signed the OCA" on August 1st, but it
is still in the "Under Review" status.
For the second step, "Socialize your change", I would like to send the
following letter to net-dev@openjdk.org:
'''
Hi OpenJDK maintainers,
I hope this message finds you well. The purpose of this letter is to
propose the integration of Multipath TCP (MPTCP) support into OpenJDK.
We have developed a set of patches to enable this functionality and are
eager to submit it for upstream inclusion. We would greatly appreciate
your feedback and opinions on this contribution.
1. Introduction
Multipath TCP (MPTCP), as standardized in RFC 8684, is a major
evolution of the TCP protocol. It enables a transport connection to use
multiple network paths simultaneously for redundancy, resilience, and
bandwidth aggregation. Since its introduction in Linux kernel v5.6, it
has become a key technology for modern networking, particularly on
mobile devices with multiple interfaces (e.g., Wi-Fi and cellular).
Key benefits include:
Bandwidth Aggregation: Combine the bandwidth of multiple network
links.
Seamless Handover: Maintain connections when switching networks
without dropping the session.
Improved Resilience: Traffic is automatically rerouted if one path
fails.
For more details, see the project website: https://mptcp.dev.
2. Technical Background
On a supporting system like 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 looks like a standard TCP socket to the
application but uses the MPTCP protocol stack underneath.
3. Proposed Java API Changes
The goal is to allow Java applications to opt-in to using MPTCP when
creating sockets, without breaking existing code. The proposed changes
are additive and backward-compatible.
The core idea is to add a boolean mptcp parameter through the API
layers, from the public Socket class down to the native system call.
4. Implementation Plan
The implementation involves changes across four layers of the JDK:
JNI Layer (sun.nio.ch.Net):
Modify Java_sun_nio_ch_Net_socket0 to accept a new jboolean mptcp
parameter.
The native implementation will be updated to use this parameter:
int protocol = mptcp == JNI_TRUE ? IPPROTO_MPTCP : 0;
fd = socket(domain, type, protocol);
NIO Layer (sun.nio.ch):
Add the mptcp parameter to the Net.socket() and Net.serverSocket()
methods.
Propagate the parameter down to the JNI call.
Socket Implementation Layer (java.net):
Add the mptcp parameter to the constructor of NioSocketImpl.
Within NioSocketImpl, pass the parameter to the Net.socket() or
Net.serverSocket() calls.
Public API Layer (java.net.Socket & java.net.ServerSocket):
Add new constructors that accept the mptcp parameter.
Example:
// Proposed new constructor
public Socket(String host, int port, boolean stream, boolean
mptcp) throws IOException {
// ... implementation that passes 'mptcp' to NioSocketImpl
}
5. Full Implementation
The complete working implementation for this proposal is available for
review:
https://github.com/openjdk/jdk/compare/master...geliangtang:jdk:master
We look forward to your valuable feedback and suggestions on this
proposal.
Best regards,
The MPTCP Upstream Developers
'''
Please review this letter for me.
Thanks,
-Geliang
> Cheers,
> Matt
next prev parent reply other threads:[~2025-09-03 6:16 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 ` [PATCH mptcp-next v2 0/3] Add MPTCP support to Java Networking API Matthieu Baerts
2025-09-03 6:16 ` Geliang Tang [this message]
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=2dc597d59d3aff65b2955f5accf0a14e2c788cf5.camel@kernel.org \
--to=geliang@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/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