From: David Miller <davem at davemloft.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH net-next 0/8] mptcp: non backup subflows pre-reqs
Date: Thu, 23 Jul 2020 11:47:40 -0700 [thread overview]
Message-ID: <20200723.114740.2116654801704929589.davem@davemloft.net> (raw)
In-Reply-To: cover.1595431326.git.pabeni@redhat.com
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
From: Paolo Abeni <pabeni(a)redhat.com>
Date: Thu, 23 Jul 2020 13:02:28 +0200
> This series contains a bunch of MPTCP improvements loosely related to
> concurrent subflows xmit usage, currently under development.
>
> The first 3 patches are actually bugfixes for issues that will become apparent
> as soon as we will enable the above feature.
>
> The later patches improve the handling of incoming additional subflows,
> improving significantly the performances in stress tests based on a high new
> connection rate.
Series applied, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: pabeni@redhat.com
Cc: netdev@vger.kernel.org, mptcp@lists.01.org
Subject: Re: [PATCH net-next 0/8] mptcp: non backup subflows pre-reqs
Date: Thu, 23 Jul 2020 11:47:40 -0700 (PDT) [thread overview]
Message-ID: <20200723.114740.2116654801704929589.davem@davemloft.net> (raw)
In-Reply-To: <cover.1595431326.git.pabeni@redhat.com>
From: Paolo Abeni <pabeni@redhat.com>
Date: Thu, 23 Jul 2020 13:02:28 +0200
> This series contains a bunch of MPTCP improvements loosely related to
> concurrent subflows xmit usage, currently under development.
>
> The first 3 patches are actually bugfixes for issues that will become apparent
> as soon as we will enable the above feature.
>
> The later patches improve the handling of incoming additional subflows,
> improving significantly the performances in stress tests based on a high new
> connection rate.
Series applied, thanks!
next reply other threads:[~2020-07-23 18:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 18:47 David Miller [this message]
2020-07-23 18:47 ` [PATCH net-next 0/8] mptcp: non backup subflows pre-reqs David Miller
-- strict thread matches above, loose matches on Subject: below --
2020-07-23 11:02 [MPTCP] [PATCH net-next 8/8] subflow: introduce and use mptcp_can_accept_new_subflow() Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
2020-07-23 11:02 [MPTCP] [PATCH net-next 7/8] subflow: use rsk_ops->send_reset() Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
2020-07-23 11:02 [MPTCP] [PATCH net-next 6/8] subflow: explicitly check for plain tcp rsk Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
2020-07-23 11:02 [MPTCP] [PATCH net-next 5/8] mptcp: cleanup subflow_finish_connect() Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
2020-07-23 11:02 [MPTCP] [PATCH net-next 4/8] mptcp: explicitly track the fully established status Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
2020-07-23 11:02 [MPTCP] [PATCH net-next 3/8] mptcp: mark as fallback even early ones Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
2020-07-23 11:02 [MPTCP] [PATCH net-next 2/8] mptcp: avoid data corruption on reinsert Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
2020-07-23 11:02 [MPTCP] [PATCH net-next 1/8] subflow: always init 'rel_write_seq' Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
2020-07-23 11:02 [MPTCP] [PATCH net-next 0/8] mptcp: non backup subflows pre-reqs Paolo Abeni
2020-07-23 11:02 ` Paolo Abeni
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=20200723.114740.2116654801704929589.davem@davemloft.net \
--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.