From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH 0/2] mptcp: partial recvmsg() refactor
Date: Fri, 13 Sep 2019 10:47:26 +0200 [thread overview]
Message-ID: <cover.1568363662.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
This 2 patches start the recvmsg() refactor discussed in last mtg.
The explicit 'duplicate data' handling in 1/2 fix some stream corruption I
observe with re-injection, and the 2nd one fix another stream corruption at
the end of the stream, still triggered by re-injection.
With the above 2 patches I still stream corruptions with re-injection, are
almost gone - even if I can still hit them with in at least a very rare corner
case.
Paolo Abeni (2):
mptcp: refactor recvmsg()
mptcp: recvmsg() should really try to deliver 'len' bytes to
user-space
net/mptcp/protocol.c | 119 +++++++++++++++++++------------------------
1 file changed, 53 insertions(+), 66 deletions(-)
--
2.21.0
reply other threads:[~2019-09-13 8: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.1568363662.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.