From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH v2 0/7] mptcp: implement retransmit infrastructure
Date: Wed, 11 Sep 2019 14:55:34 +0200 [thread overview]
Message-ID: <cover.1568206133.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
The retransmission infrastructure is now functionally completed, and I don't
observe anymore memleak/socket reference leak.
Still there are a few self-test failures I still have to investigate.
I *think* we could merge this series even with such failure pending, and fix
them later, _if_ there is agreement.
v1 -> v2
- rebased on top of "mptcp: remove token_release"
- handle unacked sequence update collision with a loop, as suggested by Mat
RFC v2 -> v1
- update msk una_seq in tcp_incoming_options() and drop old patch 3/8
- cleanup timer management
- cleanup dfrag management
Paolo Abeni (7):
mptcp: move before/after64 into the header file
mptcp: update per unacked sequence on pkt reception
mptcp: queue data for mptcp level retransmission
mptcp: introduce MPTCP retransmission timer
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 | 47 ++++-
net/mptcp/protocol.c | 396 +++++++++++++++++++++++++++++++++++++++----
net/mptcp/protocol.h | 41 +++++
3 files changed, 446 insertions(+), 38 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-11 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 12:55 Paolo Abeni [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-19 5:01 [MPTCP] [PATCH v2 0/7] mptcp: implement retransmit infrastructure Mat Martineau
2019-09-20 18:20 Matthieu Baerts
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.1568206133.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.