All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Dmytro Shytyi <dmytro@shytyi.net>,
	mathewjmartineau <mathew.j.martineau@linux.intel.com>
Cc: Davem <davem@davemloft.net>, Kuba <kuba@kernel.org>,
	mptcp <mptcp@lists.linux.dev>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v1] net: mptcp, Fast Open Mechanism
Date: Fri, 22 Oct 2021 09:22:05 +0200	[thread overview]
Message-ID: <7323f833-08e7-5b90-6175-c88696b73e63@tessares.net> (raw)
In-Reply-To: <17ca66cd439.10a0a3ce11621928.1543611905599720914@shytyi.net>

Hi Dmytro,

On 22/10/2021 07:15, Dmytro Shytyi wrote:
> This set of patches will bring "Fast Open" Option support to MPTCP.
> The aim of Fast Open Mechanism is to eliminate one round trip 
> time from a TCP conversation by allowing data to be included as 
> part of the SYN segment that initiates the connection. 
> 
> IETF RFC 8684: Appendix B.  TCP Fast Open and MPTCP.
> 
> [PATCH v1] includes "client" partial support for :
> 1. send request for cookie;
> 2. send syn+data+cookie.

Thank you for working on that and sharing this patch with us!

It looks like some modifications are going to be needed, e.g. after a
very quick look, it seems all tabs have been converted to spaces causing
the patch not being applicable on git[1]: did you not use git
format-patch to generate it? Also, some issues will be reported by
checkpatch.pl, the "reversed XMas tree" order is not respected for
variables declaration, etc.

Do you mind if we continue the discussion on MPTCP mailing list only? In
other words, without Netdev mailing list and Net maintainers, not to
bother everybody for MPTCP specific stuff?

Our usual way of working for MPTCP patches is to have the code review on
MPTCP ML only, then apply accepted patches in our tree first and once a
validation has been done, send patches later to Netdev ML for inclusion
in the -net or net-next tree.

Cheers,
Matt

[1]
https://patchew.org/logs/17ca66cd439.10a0a3ce11621928.1543611905599720914@shytyi.net/git/
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

  reply	other threads:[~2021-10-22  7:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  5:15 [PATCH net-next v1] net: mptcp, Fast Open Mechanism Dmytro Shytyi
2021-10-22  7:22 ` Matthieu Baerts [this message]
2021-10-22  8:21   ` Dmytro Shytyi
2021-10-22  9:22 ` Matthieu Baerts
2021-10-22 18:26   ` Mat Martineau
2021-10-25 11:36     ` Dmytro Shytyi
2021-10-25 11:34   ` Dmytro Shytyi
2021-10-25 12:37     ` Matthieu Baerts
2021-12-05 20:59       ` Dmytro Shytyi
2022-01-08 17:58         ` Dmytro Shytyi
2022-01-10 11:17           ` Paolo Abeni

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=7323f833-08e7-5b90-6175-c88696b73e63@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --cc=davem@davemloft.net \
    --cc=dmytro@shytyi.net \
    --cc=kuba@kernel.org \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    /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.