netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Davide Caratti <dcaratti@redhat.com>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>,
	Matthieu Baerts <matthieu.baerts@tessares.net>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, mptcp@lists.01.org
Subject: [PATCH net-next 0/6] MPTCP: improve fallback to TCP
Date: Mon, 29 Jun 2020 22:26:19 +0200	[thread overview]
Message-ID: <cover.1593461586.git.dcaratti@redhat.com> (raw)

there are situations where MPTCP sockets should fall-back to regular TCP:
this series reworks the fallback code to pursue the following goals:

1) cleanup the non fallback code, removing most of 'if (<fallback>)' in
   the data path
2) improve performance for non-fallback sockets, avoiding locks in poll()

further work will also leverage on this changes to achieve:

a) more consistent behavior of gestockopt()/setsockopt() on passive sockets
   after fallback
b) support for "infinite maps" as per RFC8684, section 3.7

the series is made of the following items:

- patch 1 lets sendmsg() / recvmsg() / poll() use the main socket also
  after fallback
- patch 2 fixes 'simultaneous connect' scenario after fallback. The
  problem was present also before the rework, but the fix is much easier
  to implement after patch 1
- patch 3, 4, 5 are clean-ups for code that is no more needed after the
  fallback rework
- patch 6 fixes a race condition between close() and poll(). The problem
  was theoretically present before the rework, but it became almost
  systematic after patch 1

Davide Caratti (2):
  net: mptcp: improve fallback to TCP
  mptcp: fallback in case of simultaneous connect

Paolo Abeni (4):
  mptcp: check for plain TCP sock at accept time
  mptcp: create first subflow at msk creation time
  mptcp: __mptcp_tcp_fallback() returns a struct sock
  mptcp: close poll() races

 net/mptcp/options.c  |   9 +-
 net/mptcp/protocol.c | 267 ++++++++++++++-----------------------------
 net/mptcp/protocol.h |  43 +++++++
 net/mptcp/subflow.c  |  57 ++++++---
 4 files changed, 175 insertions(+), 201 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-06-29 20:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 20:26 Davide Caratti [this message]
2020-06-29 20:26 ` [PATCH net-next 1/6] net: mptcp: improve fallback to TCP Davide Caratti
2020-06-29 23:29   ` Mat Martineau
2020-06-29 20:26 ` [PATCH net-next 2/6] mptcp: fallback in case of simultaneous connect Davide Caratti
2020-06-29 23:29   ` Mat Martineau
2020-06-29 20:26 ` [PATCH net-next 3/6] mptcp: check for plain TCP sock at accept time Davide Caratti
2020-06-29 23:30   ` Mat Martineau
2020-06-29 20:26 ` [PATCH net-next 4/6] mptcp: create first subflow at msk creation time Davide Caratti
2020-06-29 23:30   ` Mat Martineau
2020-06-29 20:26 ` [PATCH net-next 5/6] mptcp: __mptcp_tcp_fallback() returns a struct sock Davide Caratti
2020-06-29 23:30   ` Mat Martineau
2020-06-29 20:26 ` [PATCH net-next 6/6] mptcp: close poll() races Davide Caratti
2020-06-29 23:31   ` Mat Martineau
2020-06-30  0:29 ` [PATCH net-next 0/6] MPTCP: improve fallback to TCP David Miller

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.1593461586.git.dcaratti@redhat.com \
    --to=dcaratti@redhat.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.01.org \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).