All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH 0/3] mptcp: just another recvmsg refactor
Date: Wed, 16 Oct 2019 09:39:57 +0200	[thread overview]
Message-ID: <fbb84d58-9078-773e-ce7e-2b0f9792a10a@tessares.net> (raw)
In-Reply-To: 009d27af4eb0b39293a215013596e2c445a0be7b.camel@redhat.com

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

Hi Paolo,

On 15/10/2019 22:39, Paolo Abeni wrote:
> On Tue, 2019-10-15 at 17:44 +0200, Paolo Abeni wrote:
>> I think this 3 patches should be squashed into
>> "mptcp: Implement MPTCP receive path", but the resulting one will be likely
>> too huge; possibly splitting the resulting code in 2 different patches would
>> be nicer. Additionally "mptcp: Implement MPTCP receive path" has some chunks
>> that should be likely moved to some other patches (e.g. ULP RCU fixes).
>>
>> What if - after the eventuall accept - I publish the resulting code of the
>> above squashing somewhere?
> 
> Since I'm an incurable optimist, I went ahead and pushed the rebase
> here:

Thank you for this work!

> https://github.com/pabeni/mptcp/tree/mptcp-proposal-recvmsg_rebase_7
> 
> Squashed:
> "mptcp: flush duplicate data at data_ready() time"
> and
> "mptcp: move some helper into the header file"
>    into "mptcp: Implement MPTCP receive path"
>      (and rewrote the commit message)
> 
> "mptcp: harmonize locking on all socket operations."
>    partially in
>      "mptcp: Associate MPTCP context with TCP socket"
>    and partially in
>      "mptcp: Create SUBFLOW socket for incoming connections"
> 
> Moved the RCU bits from "mptcp: Implement MPTCP receive path"
> into:
>    "mptcp: Associate MPTCP context with TCP socket"
> 
> Moved the options/ack_seq bits from "mptcp: Implement MPTCP receive
> path" into:
>    "mptcp: Write MPTCP DSS headers to outgoing data packets"
> 
> Rebased "mptcp: recvmsg() can drain data from multiple subflows" on top
> of "mptcp: Implement MPTCP receive path"
> 
> Removed a few intentation issue.
> 
> I checked for build issue only on the modified patches.
> 
> The overall diff from current export branch plus the pending patches is
> reported below.

Which ref of the "export" branch did you use? This branch has been 
overridden 3 times yesterday:
- around 3.52am: a rebase on latest net-next
- around 2.42pm: to include "selftests: allow compilation on older systems"
- around 5.23pm: to include "mptcp:pm: some cleanup"

Note that a rebase on latest net-next was done this night by the CI but 
that's easy to re-do.

Will you include the change proposed by Mat in a new rebase?

Cheers,
Matt
-- 
Matthieu Baerts | R&D Engineer
matthieu.baerts(a)tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium

             reply	other threads:[~2019-10-16  7:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  7:39 Matthieu Baerts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-16 20:06 [MPTCP] Re: [PATCH 0/3] mptcp: just another recvmsg refactor Paolo Abeni
2019-10-16 18:09 Mat Martineau
2019-10-16 16:48 Matthieu Baerts
2019-10-16 14:07 Matthieu Baerts
2019-10-16 13:54 Paolo Abeni
2019-10-16 11:14 Matthieu Baerts
2019-10-16 10:02 Matthieu Baerts
2019-10-16  8:58 Paolo Abeni
2019-10-16  8:37 Matthieu Baerts
2019-10-16  8:22 Paolo Abeni
2019-10-15 20:39 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=fbb84d58-9078-773e-ce7e-2b0f9792a10a@tessares.net \
    --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.