From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [RFC PATCH v2 0/8] mptcp: implement retransmit infrastructure
Date: Thu, 22 Aug 2019 15:47:37 +0200 [thread overview]
Message-ID: <cover.1566481012.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
Note this is still early draft, only lightly tested. It builds and somtimes
it passes the selftests
In addition to the first iteration now:
- implement actual retransmission infrastructure and trigger it when MPTCP
timer expires (patches 7,8)
- fixes several bugs in many patches - but others are still there
RFC v1:
- updates the MPTCP unacked sequence number (patches 1-3) on sendmsg()
- also try to cope with 32 bit sequence number
- queue data (page frags) in MPTCP retransmission queue
- cleanup acked data from retransmission queue and schedule a timeout to
update MPTCP unacked sequence number (patch 5)
Open points:
- IIRC, the RFC mandate to always retransmit even on the failing subflow (?!?)
why? Should we preserve the original subflow seq number, so that
retransmission there will get the same mapping as the original packet?
Paolo Abeni (8):
mptcp: move before/after64 into the header file
mptcp: update per subflow unacked sequence on pkt reception
mptcp: update msk unacked sequence in sendmsg()
mptcp: queue data for mptcp level retransmission
mptcp: use retransmission timer to update msk una
mptcp: implement memory accounting for mptcp rtx queue
mptcp: rework mptcp_sendmsg_frag to accept optional dfrag
mptcp: implement and use MPTCP-level retransmission
net/mptcp/options.c | 31 +++-
net/mptcp/protocol.c | 405 +++++++++++++++++++++++++++++++++++++++----
net/mptcp/protocol.h | 41 +++++
3 files changed, 437 insertions(+), 40 deletions(-)
--
2.21.0
reply other threads:[~2019-08-22 13:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1566481012.git.pabeni@redhat.com \
--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.