Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FR] Multipath TCP awareness in libuv.jl #38184

Open
mkschulze opened this issue Oct 26, 2020 · 1 comment
Open

[FR] Multipath TCP awareness in libuv.jl #38184

mkschulze opened this issue Oct 26, 2020 · 1 comment
Labels
I/O Involving the I/O subsystem: libuv, read, write, etc. Sockets speculative Whether the change will be implemented is speculative upstream The issue is with an upstream dependency, e.g. LLVM

Comments

@mkschulze
Copy link

mkschulze commented Oct 26, 2020 •
edited

Just want to mention the ongoing work by the Mulipath TCP group. It was suggested to raise a discussion here maybe, to evaluate this once it's ready.

I summed up some information here as well: https://discourse.julialang.org/t/multipath-tcp-awareness-in-sockets-jl/48952

#38166 [FR] MPTCP-awareness in Sockets.jl
@mkschulze mkschulze changed the title [FR] Multipath TCP (MPTCP) awareness in libuv.jl [FR] Multipath TCP awareness in libuv.jl Oct 26, 2020
@StefanKarpinski StefanKarpinski added speculative Whether the change will be implemented is speculative I/O Involving the I/O subsystem: libuv, read, write, etc. upstream The issue is with an upstream dependency, e.g. LLVM labels Oct 26, 2020
@StefanKarpinski
Copy link
Sponsor Member

Basically blocked until operating systems and libuv add support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
I/O Involving the I/O subsystem: libuv, read, write, etc. Sockets speculative Whether the change will be implemented is speculative upstream The issue is with an upstream dependency, e.g. LLVM
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@StefanKarpinski @mkschulze