From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH net-next 0/3] add MP_PRIO, MP_FAIL and MP_FASTCLOSE suboptions handling
Date: Thu, 18 Jun 2020 14:27:37 +0800 [thread overview]
Message-ID: <20200618062737.GA21303@OptiPlex> (raw)
In-Reply-To: 04ae76d9-231a-de8e-ad33-1e4e80bb314c@tessares.net
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
On Tue, Jun 16, 2020 at 05:18:56PM +0200, Matthieu Baerts wrote:
> Hi Geliang
>
> On 16/06/2020 08:47, Geliang Tang wrote:
> > Add handling for sending and receiving the MP_PRIO, MP_FAIL, and
> > MP_FASTCLOSE suboptions.
>
> Thank you for the patches!
>
> Unfortunately, I don't think it would be wise to accept them now: for the
> moment, these suboptions are ignored at the reception. If we accept them and
> change some variables like you did, we would need to make sure the kernel is
> still acting correctly. In other words, we would need tests:
> * For MP_PRIO, there are still quite some works to do regarding the
> scheduling of the packets between the different MPTCP subflows to do before
> supporting this.
> * For MP_FAIL, we should forward the info to the path manager.
> * For MP_FASTCLOSE, we should close connections and ACK this.
>
> Also, net-next is closed for the moment:
> http://vger.kernel.org/~davem/net-next.html
>
> I would suggest you to discuss about that on MPTCP mailing list. We also
> have meetings every Thursday. New devs are always welcome to contribute to
> new features and bug-fixes!
>
Hi Matt,
Thanks for your reply. I will do these tests and improve my patches.
-Geliang
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
WARNING: multiple messages have this Message-ID (diff)
From: Geliang Tang <geliangtang@gmail.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Mat Martineau <mathew.j.martineau@linux.intel.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, mptcp@lists.01.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] add MP_PRIO, MP_FAIL and MP_FASTCLOSE suboptions handling
Date: Thu, 18 Jun 2020 14:27:37 +0800 [thread overview]
Message-ID: <20200618062737.GA21303@OptiPlex> (raw)
In-Reply-To: <04ae76d9-231a-de8e-ad33-1e4e80bb314c@tessares.net>
On Tue, Jun 16, 2020 at 05:18:56PM +0200, Matthieu Baerts wrote:
> Hi Geliang
>
> On 16/06/2020 08:47, Geliang Tang wrote:
> > Add handling for sending and receiving the MP_PRIO, MP_FAIL, and
> > MP_FASTCLOSE suboptions.
>
> Thank you for the patches!
>
> Unfortunately, I don't think it would be wise to accept them now: for the
> moment, these suboptions are ignored at the reception. If we accept them and
> change some variables like you did, we would need to make sure the kernel is
> still acting correctly. In other words, we would need tests:
> * For MP_PRIO, there are still quite some works to do regarding the
> scheduling of the packets between the different MPTCP subflows to do before
> supporting this.
> * For MP_FAIL, we should forward the info to the path manager.
> * For MP_FASTCLOSE, we should close connections and ACK this.
>
> Also, net-next is closed for the moment:
> http://vger.kernel.org/~davem/net-next.html
>
> I would suggest you to discuss about that on MPTCP mailing list. We also
> have meetings every Thursday. New devs are always welcome to contribute to
> new features and bug-fixes!
>
Hi Matt,
Thanks for your reply. I will do these tests and improve my patches.
-Geliang
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
next reply other threads:[~2020-06-18 6:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 6:27 Geliang Tang [this message]
2020-06-18 6:27 ` [PATCH net-next 0/3] add MP_PRIO, MP_FAIL and MP_FASTCLOSE suboptions handling Geliang Tang
-- strict thread matches above, loose matches on Subject: below --
2020-06-18 8:06 [MPTCP] " Matthieu Baerts
2020-06-18 8:06 ` Matthieu Baerts
2020-06-16 15:18 [MPTCP] " Matthieu Baerts
2020-06-16 15:18 ` Matthieu Baerts
2020-06-16 6:47 [MPTCP] [PATCH net-next 3/3] mptcp: add MP_FASTCLOSE suboption handling Geliang Tang
2020-06-16 6:47 ` Geliang Tang
2020-06-16 6:47 [MPTCP] [PATCH net-next 2/3] mptcp: add MP_FAIL " Geliang Tang
2020-06-16 6:47 ` Geliang Tang
2020-06-16 6:47 [MPTCP] [PATCH net-next 1/3] mptcp: add MP_PRIO " Geliang Tang
2020-06-16 6:47 ` Geliang Tang
2020-06-16 6:47 [MPTCP] [PATCH net-next 0/3] add MP_PRIO, MP_FAIL and MP_FASTCLOSE suboptions handling Geliang Tang
2020-06-16 6:47 ` 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=20200618062737.GA21303@OptiPlex \
--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.