From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [PRE-RFC 0/6] mptcp: implement retransmit infrastructure
Date: Mon, 19 Aug 2019 16:35:33 +0200 [thread overview]
Message-ID: <20190819143533.GJ2588@breakpoint.cc> (raw)
In-Reply-To: 848b15465394deaa1ca7d5237dea15ff776e2b80.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> On Mon, 2019-08-19 at 13:06 +0200, Florian Westphal wrote:
> > Is this for future failover case?
>
> Yes, with a single subflow, we should not use MPTCP-level
> retransmission, it should be triggered by scenarios using failover
> and/or multiple concurrent substream.
>
> Well, to be 110% honest, I think that with a wrong/less than perfect
> MPTCP-level retransmission heuristic we could end-up retransmitting
> even with a single flow: since the receiver sends MPTCP-level ack only
> after that the user-space read the data, a slow receiver user-space
> could trigger the timeout on the sender (and now that I have wrote it
> down, it looks a quite bad thing to me :(
Its not ideal, but I don't think its something that needs
to be addressed *right now*.
> [If I'm not completely lost, this is the only question left without an
> answer right???]
Yes, thanks.
next reply other threads:[~2019-08-19 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 14:35 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-19 13:02 [MPTCP] [PRE-RFC 0/6] mptcp: implement retransmit infrastructure Paolo Abeni
2019-08-19 11:06 Florian Westphal
2019-08-16 16:47 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=20190819143533.GJ2588@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.