From: Krystad, Peter <peter.krystad at intel.com>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [RFC 1/1] Add MPTCP code to work with the modified TCP code
Date: Wed, 21 Mar 2018 20:18:04 +0000 [thread overview]
Message-ID: <1521663482.23414.4.camel@intel.com> (raw)
In-Reply-To: ae22c65d-23bb-74bf-abc1-ab81a7334325@oracle.com
[-- Attachment #1: Type: text/plain, Size: 2395 bytes --]
Hi Rao -
On Thu, 2018-03-01 at 12:02 -0800, Rao Shoaib wrote:
>
> On 03/01/2018 11:20 AM, Christoph Paasch wrote:
> > On 28/02/18 - 16:49:52, rao.shoaib(a)oracle.com wrote:
> > > From: Rao Shoaib <rao.shoaib(a)oracle.com>
> > >
> > > Signed-off-by: Rao Shoaib <rao.shoaib(a)oracle.com>
> > > ---
> > > include/net/mptcp.h | 1474 +++++++++++++++++++++
> > > include/net/mptcp_v4.h | 56 +
> > > include/net/mptcp_v6.h | 56 +
> > > include/net/netns/mptcp.h | 52 +
> > > net/Kconfig | 1 +
> > > net/Makefile | 1 +
> > > net/mptcp/Kconfig | 129 ++
> > > net/mptcp/Makefile | 22 +
> > > net/mptcp/mptcp_balia.c | 267 ++++
> > > net/mptcp/mptcp_binder.c | 487 +++++++
> > > net/mptcp/mptcp_coupled.c | 270 ++++
> > > net/mptcp/mptcp_ctrl.c | 2981
> > > ++++++++++++++++++++++++++++++++++++++++++
> > > net/mptcp/mptcp_fullmesh.c | 1877 ++++++++++++++++++++++++++
> > > net/mptcp/mptcp_input.c | 2970
> > > +++++++++++++++++++++++++++++++++++++++++
> > > net/mptcp/mptcp_ipv4.c | 345 +++++
> > > net/mptcp/mptcp_ipv6.c | 316 +++++
> > > net/mptcp/mptcp_ndiffports.c | 169 +++
> > > net/mptcp/mptcp_ofo_queue.c | 177 +++
> > > net/mptcp/mptcp_olia.c | 309 +++++
> > > net/mptcp/mptcp_output.c | 1837 ++++++++++++++++++++++++++
> > > net/mptcp/mptcp_pm.c | 178 +++
> > > net/mptcp/mptcp_redundant.c | 268 ++++
> > > net/mptcp/mptcp_rr.c | 301 +++++
> > > net/mptcp/mptcp_sched.c | 597 +++++++++
> > > net/mptcp/mptcp_wvegas.c | 268 ++++
> > > 25 files changed, 15408 insertions(+)
> >
> > Please read the sections "Separate your changes" and "E-mail size"
> > of
> > process/submitting-patches.rst.
>
> If you are worried about the size than do not use it. I am not
> asking
> for review, just posting it in case someone wants to try out MPTCP
> with
> my changes.
>
It seems now you are asking for a review. Can we get this as a patch
relative to the existing MPTCP implementation so we can see your work?
Thanks,
Peter.
> Shoaib
> > Christoph
> >
>
> _______________________________________________
> mptcp mailing list
> mptcp(a)lists.01.org
> https://lists.01.org/mailman/listinfo/mptcp
next reply other threads:[~2018-03-21 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 20:18 Krystad, Peter [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-22 19:00 [MPTCP] [RFC 1/1] Add MPTCP code to work with the modified TCP code Rao Shoaib
2018-03-22 18:56 Krystad, Peter
2018-03-22 18:12 Rao Shoaib
2018-03-21 21:22 Rao Shoaib
2018-03-01 20:02 Rao Shoaib
2018-03-01 19:20 Christoph Paasch
2018-03-01 0:49 rao.shoaib
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=1521663482.23414.4.camel@intel.com \
--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.