From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH mptcp-next 0/3] mptcp: improve mptcp release callback
Date: Tue, 09 Feb 2021 12:42:38 +0100 [thread overview]
Message-ID: <cover.1612869198.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
The current callback implementation is probe to some race
and still use some suboptimal code from older times.
This series clean-up the code a bit, fixing the race
and hopefully simplifying future wider usage of delegated
actions
Paolo Abeni (3):
mptcp: factor out __mptcp_retrans helper()
mptcp: fix race in release_cb
mptcp: clean-up the rtx path.
net/mptcp/protocol.c | 164 +++++++++++++++++++++----------------------
net/mptcp/protocol.h | 1 +
2 files changed, 81 insertions(+), 84 deletions(-)
--
2.26.2
reply other threads:[~2021-02-09 11:42 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.1612869198.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.