All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: [RFC PATCH 0/3] mptcp: improve accept() and disconnect()
Date: Fri,  5 Nov 2021 11:49:09 +0100	[thread overview]
Message-ID: <cover.1636107361.git.pabeni@redhat.com> (raw)

As outlined in the public mtg, mptcp_accept() is currently quite
suboptimal, both from performance and code complexity

This series tries to clean it up, enforcing a wider lifetime for
the initial subflow, so that we don't need to acquire additional
references there.

To reach such goal we need to properly define the disconnect()
behavior, which is currently quite incomplete.

Some additional self-tests is likely required, 

Paolo Abeni (3):
  mptcp: never allow the PM to close a listener subflow
  mptcp: full disconnect implementation
  mptcp: cleanup accept and poll

 net/mptcp/pm.c         |  10 ++--
 net/mptcp/pm_netlink.c |   3 ++
 net/mptcp/protocol.c   | 120 ++++++++++++++++++++++++++---------------
 net/mptcp/protocol.h   |  15 +++++-
 net/mptcp/subflow.c    |   1 -
 net/mptcp/token.c      |   1 +
 6 files changed, 102 insertions(+), 48 deletions(-)

-- 
2.26.3


             reply	other threads:[~2021-11-05 10:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 10:49 Paolo Abeni [this message]
2021-11-05 10:49 ` [RFC PATCH 1/3] mptcp: never allow the PM to close a listener subflow Paolo Abeni
2021-11-08 16:56   ` Matthieu Baerts
2021-11-09 14:38     ` Paolo Abeni
2021-11-09 14:55       ` Matthieu Baerts
2021-11-05 10:49 ` [RFC PATCH 2/3] mptcp: full disconnect implementation Paolo Abeni
2021-11-05 10:49 ` [RFC PATCH 3/3] mptcp: cleanup accept and poll Paolo Abeni
2021-11-05 10:59   ` mptcp: cleanup accept and poll: Build Failure MPTCP CI
2021-11-06  0:27 ` [RFC PATCH 0/3] mptcp: improve accept() and disconnect() Mat Martineau

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.1636107361.git.pabeni@redhat.com \
    --to=pabeni@redhat.com \
    --cc=mptcp@lists.linux.dev \
    /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.