All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Paasch <cpaasch at apple.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8
Date: Thu, 08 Oct 2020 11:28:24 -0700	[thread overview]
Message-ID: <20201008182824.GB34635@MacBook-Pro.local> (raw)
In-Reply-To: CAO=PVE8JUAg8An96p0VVjL0GdVEd97hH27mpBGjUbq95j317HA@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

+MPTCP upstreaming list

Hello Yoshi,

On 10/08/20 - 01:44, yoshi nishida wrote:
> Hello,
> 
> It's really great to see mptcp codes in main stream.  So, I've tried
> to use it with kernel 5.8 in ubuntu20.10.
> However, as far as I've checked, the mptcp in the kernel seems to be
> different from the one in the repo.

The repo, you mean the repo of multipath-tcp.org kernel? Yes, they are
entirely different. The MPTCP implementation in upstream Linux (5.6+) is a
complete rewrite.

> I am not sure how to set scheduler
> or path manager with this.

It is currently not possible to select different schedulers on the upstream
implementation.

For path-management there is an ip-mptcp interface that allows you to add
subflows and addresses: https://man7.org/linux/man-pages/man8/ip-mptcp.8.html


Christoph

> Does anyone know about the differences?
> Sorry if I overlooked something.
> 
> Thanks,
> --
> Yoshi

> MPTCP-developpers Mailing-List
> Visit http://multipath-tcp.org to access the source-code of MPTCP in the Linux Kernel
> 
> To Unsubscribe, visit https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev
> 

             reply	other threads:[~2020-10-08 18:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 18:28 Christoph Paasch [this message]
2020-10-14  9:02 [MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8 yoshi nishida
2020-10-14  9:13 Matthieu Baerts
2020-10-15  8:09 yoshi nishida
2020-10-15  8:30 Matthieu Baerts
2020-10-16  8:31 yoshi nishida
2020-10-20 14:19 Sandeep Irlanki
2020-10-20 14:36 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=20201008182824.GB34635@MacBook-Pro.local \
    --to=unknown@example.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.