From: Geliang Tang <geliang@kernel.org>
To: Alan Bateman <alan.bateman@oracle.com>,
net-dev@openjdk.org, "nio-dev@openjdk.org" <nio-dev@openjdk.org>
Cc: Matthieu Baerts <matttbe@kernel.org>,
Mat Martineau <martineau@kernel.org>,
mptcp@lists.linux.dev, Gang Yan <yangang@kylinos.cn>,
Xiang Gao <gaoxiang@kylinos.cn>,
core-libs-dev@openjdk.org
Subject: Re: Add Multipath TCP (MPTCP) Support to the Java Networking API
Date: Tue, 23 Sep 2025 17:55:15 +0800 [thread overview]
Message-ID: <2baf027907da32f096cb522691e5d92c454000e4.camel@kernel.org> (raw)
In-Reply-To: <2b699d6c-d05b-4445-9448-99348eebdf4a@oracle.com>
Hi Alan,
Thanks for your reply.
On Thu, 2025-09-18 at 12:30 +0100, Alan Bateman wrote:
>
> On 18/09/2025 08:36, Geliang Tang wrote:
>
> >
> > I have completed the implementation. Thanks to Xiang Gao and Gang
> > Yan
> > for their help. I added a new option named TCP_MPTCPIFY in
> > jdk.net.ExtendedSocketOptions (the name was chosen to align with
> > 'mptcpize' tool in mptcpd and 'mptcpify' in BCC). When this option
> > is
> > set, it calls the JNI function mptcpify0.
> >
> > Following your suggestion, mptcpify0 is implemented by referencing
> > Java_sun_net_sdp_SdpSupport_convert0. It creates a new MPTCP
> > socket,
> > uses dup2 to duplicate it, and then closes the redundant socket.
> >
> > I have added your tag in the patch:
> >
> > Suggested-by: Alan Bateman <alan.bateman@oracle.com>
> >
> > I also included a test example for this option. All modifications
> > can
> > be found here:
> >
> > https://github.com/openjdk/jdk/compare/master...geliangtang:jdk:master
> >
> > Please provide any feedback or suggestions. As for the next steps,
> > should I create a new issue for this feature and submit a proper
> > pull
> > request?
> >
>
> Thanks for confirming that the direction suggested works. This at
> least demonstrates a feasible direction that does not impact the
> standard API.
>
> As regards next steps then I think start a thread on net-dev to try
> to get input. I think it would be useful to show potential scenarios
> where it would be useful and what performance benefits might come
> from it. I think also useful to talk about whether this is something
> that an application has to opt into, maybe there are other
> configuration approaches that would not require application changes?
>
> I think it would be useful to discuss testing. If this feature were
> integrated into the JDK then how would it be tested? Who would test
> and maintain it? There is a JDK release every 6 months, is someone
> going test it with each release?
>
> If it goes ahead then there the name of the extended socket option
> and its API docs will need discussion. Details around state will need
> to be specified, would it be supported to set TCP_MPTCP when bound or
> connected, does it make sense to ever attempt to set it to false
> after setting it to true (these are just examples of the details that
> will need to be specified, they are not important right now).
Following your suggestion, I have started a new thread on net-dev:
Add Extended MPTCP (Multipath TCP) Socket Option Support to OpenJDK
https://mail.openjdk.org/pipermail/net-dev/2025-September/028085.html
Thanks,
-Geliang
>
> -Alan.
>
>
next prev parent reply other threads:[~2025-09-23 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 8:43 Add Multipath TCP (MPTCP) Support to the Java Networking API Geliang Tang
[not found] ` <7403952e-14c1-4ba2-871e-0e2174fd5167@oracle.com>
2025-09-05 10:05 ` Geliang Tang
2025-09-05 10:11 ` Geliang Tang
2025-09-18 7:36 ` Geliang Tang
[not found] ` <2b699d6c-d05b-4445-9448-99348eebdf4a@oracle.com>
2025-09-23 9:55 ` Geliang Tang [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-05 1:43 Geliang Tang
2025-09-05 9:00 ` Geliang Tang
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=2baf027907da32f096cb522691e5d92c454000e4.camel@kernel.org \
--to=geliang@kernel.org \
--cc=alan.bateman@oracle.com \
--cc=core-libs-dev@openjdk.org \
--cc=gaoxiang@kylinos.cn \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=net-dev@openjdk.org \
--cc=nio-dev@openjdk.org \
--cc=yangang@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