From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v3 0/6] mptcp: update mptcp ack sequence from work queue
Date: Wed, 19 Feb 2020 13:43:18 +0100 [thread overview]
Message-ID: <20200219124318.GL19559@breakpoint.cc> (raw)
In-Reply-To: cdfd6084ad257bfd74de8c4ae36aab914504e3a0.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> On Tue, 2020-02-18 at 13:21 +0100, Florian Westphal wrote:
> > This is v3 of the attempt to allow mptcp to update its ack-sequence
> > number even if userspace doesn't call recv() for some time.
> > This includes a change to patch 2/6 to address a theoretical race when
> > two subflows deliver same data: previous version may have discarded the
> > additional data correctly, but would leave EPOLLIN indication enabled,
> > even though all data has to be tossed as duplicate.
> >
> > Rest of patches is unchanged.
>
> The series LGTM.
>
> My understanding is that the patches are not going to be squashed, just
> sent directly U/S, right?
I don't mind, whatever seems more appropriate when we roll this
out to netdev.
3 and 6 could be squashed into #2.
But for now I think they can be applied as-is.
> If so I think the commit message in patch 2 and 3 should be cleaned-up
> a bit.
3 is too brief, yes, but whats missing in #2?
next reply other threads:[~2020-02-19 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 12:43 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 23:23 [MPTCP] Re: [PATCH v3 0/6] mptcp: update mptcp ack sequence from work queue Florian Westphal
2020-02-19 15:16 Paolo Abeni
2020-02-19 12:36 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=20200219124318.GL19559@breakpoint.cc \
--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.