mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dmytro Shytyi <dmytro@shytyi.net>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [RFC PATCH mptcp-next v11 0/4] mptcp: Fast Open: Initiator
Date: Tue, 27 Sep 2022 05:22:47 +0200	[thread overview]
Message-ID: <2775bf12-c6e4-07c7-d620-97136c19479d@shytyi.net> (raw)
In-Reply-To: <8a9daf89c1df988d86eac05a37c357f1a837d455.camel@redhat.com>

Hello Paolo,

I added the patches 4,5,6 from v9 and fixes based on the feedback. Will 
be present in the next version.

On 9/26/2022 4:52 PM, Paolo Abeni wrote:
> On Mon, 2022-09-26 at 01:25 +0200, Dmytro Shytyi wrote:
>> These patches focus on the Initiator side.
>> These patches implement: sendto(..., ..., ..., MSG_FASTOPEN, ..., ...);
>> We would like to credit Paulo Abeni, Mat Martineau, Matthieu Baerts and
>> Benjamin Hesmans for advices and ideas that improved these patches.
>> Without this collaboration this state of work would not be presented.
>>
>> Origins of these patches were in the root of discovery of the
>> possibility to _reuse the TCP FASTOPEN option in the linux
>> upstream MPTCP_ (First commit was sent to the mailing list on 22 OCT
>> 2021: see https://lore.kernel.org/mptcp/
>> 17ca66cd439.10a0a3ce11621928.1543611905599720914@shytyi.net/').
>>
>> Dmytro Shytyi (4):
>>    mptcp: add mptcp_setsockopt_fastopen
>>    mptcp: add mptcp_stream_connect to *.h
>>    mptcp: add mptcp_subflow_conn_sock()
>>    mptcp: reuse tcp_sendmsg_fastopen()
>>
>>   include/net/mptcp.h  |  9 +++++++++
>>   include/net/tcp.h    |  3 +++
>>   net/ipv4/tcp.c       | 21 ++++++++++++++++-----
>>   net/mptcp/Makefile   |  2 +-
>>   net/mptcp/fastopen.c | 37 +++++++++++++++++++++++++++++++++++++
>>   net/mptcp/protocol.c | 35 +++++++++++++++++++++++++++++++----
>>   net/mptcp/protocol.h |  5 +++++
>>   net/mptcp/sockopt.c  |  3 +++
>>   8 files changed, 105 insertions(+), 10 deletions(-)
>>   create mode 100644 net/mptcp/fastopen.c
>>
> Plase, on the next iteration include the rx-path-related patches (e.g.
> patches 4, 5 and 6 from v9, updated with the relevant feedback).
>
> Thanks,
>
> Paolo
>
>

      reply	other threads:[~2022-09-27  3:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 23:25 [RFC PATCH mptcp-next v11 0/4] mptcp: Fast Open: Initiator Dmytro Shytyi
2022-09-25 23:25 ` [RFC PATCH mptcp-next v11 1/4] mptcp: add mptcp_setsockopt_fastopen Dmytro Shytyi
2022-09-26 14:50   ` Paolo Abeni
2022-09-26 15:01     ` Matthieu Baerts
2022-09-27  4:01       ` Dmytro Shytyi
2022-09-27 15:22         ` Matthieu Baerts
2022-09-27 21:56           ` Dmytro Shytyi
2022-09-25 23:25 ` [RFC PATCH mptcp-next v11 2/4] mptcp: add mptcp_stream_connect to *.h Dmytro Shytyi
2022-09-25 23:26 ` [RFC PATCH mptcp-next v11 3/4] mptcp: add mptcp_subflow_conn_sock() Dmytro Shytyi
2022-09-26 17:11   ` Matthieu Baerts
2022-09-27 15:11     ` Dmytro Shytyi
2022-09-25 23:26 ` [RFC PATCH mptcp-next v11 4/4] mptcp: reuse tcp_sendmsg_fastopen() Dmytro Shytyi
2022-09-26 14:46   ` Paolo Abeni
2022-09-27 15:09     ` Dmytro Shytyi
2022-09-26 14:52 ` [RFC PATCH mptcp-next v11 0/4] mptcp: Fast Open: Initiator Paolo Abeni
2022-09-27  3:22   ` Dmytro Shytyi [this message]

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=2775bf12-c6e4-07c7-d620-97136c19479d@shytyi.net \
    --to=dmytro@shytyi.net \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).