From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH net-next 0/5] mptcp: re-enable sndbuf autotune
Date: Wed, 20 Jan 2021 11:40:35 +0100 [thread overview]
Message-ID: <cover.1610991949.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
The sendbuffer autotuning was unintentionally disabled as a
side effect of the recent workqueue removal refactor. These
patches re-enable id, with some extra care: with autotuning
enable/large send buffer we need a more accurate packet
scheduler to be able to use efficiently the available
subflow bandwidth, especially when the subflows have
different capacities.
The first patch cleans-up subflow socket handling, making
the actual re-enable (patch 2) simpler.
Patches 3 and 4 improve the packet scheduler, to better cope
with non trivial scenarios and large send buffer.
Finally patch 5 adds and uses some infrastructure to avoid
the workqueue usage for the packet scheduler operations introduced
by the previous patches.
Paolo Abeni (5):
mptcp: always graft subflow socket to parent
mptcp: re-enable sndbuf autotune
mptcp: do not queue excessive data on subflows
mptcp: schedule work for better snd subflow selection
mptcp: implement delegated actions
net/mptcp/protocol.c | 176 ++++++++++++++++++++++++++++---------------
net/mptcp/protocol.h | 72 ++++++++++++++++++
net/mptcp/subflow.c | 49 +++++++++++-
3 files changed, 234 insertions(+), 63 deletions(-)
--
2.26.2
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
mptcp@lists.01.org
Subject: [PATCH net-next 0/5] mptcp: re-enable sndbuf autotune
Date: Wed, 20 Jan 2021 11:40:35 +0100 [thread overview]
Message-ID: <cover.1610991949.git.pabeni@redhat.com> (raw)
The sendbuffer autotuning was unintentionally disabled as a
side effect of the recent workqueue removal refactor. These
patches re-enable id, with some extra care: with autotuning
enable/large send buffer we need a more accurate packet
scheduler to be able to use efficiently the available
subflow bandwidth, especially when the subflows have
different capacities.
The first patch cleans-up subflow socket handling, making
the actual re-enable (patch 2) simpler.
Patches 3 and 4 improve the packet scheduler, to better cope
with non trivial scenarios and large send buffer.
Finally patch 5 adds and uses some infrastructure to avoid
the workqueue usage for the packet scheduler operations introduced
by the previous patches.
Paolo Abeni (5):
mptcp: always graft subflow socket to parent
mptcp: re-enable sndbuf autotune
mptcp: do not queue excessive data on subflows
mptcp: schedule work for better snd subflow selection
mptcp: implement delegated actions
net/mptcp/protocol.c | 176 ++++++++++++++++++++++++++++---------------
net/mptcp/protocol.h | 72 ++++++++++++++++++
net/mptcp/subflow.c | 49 +++++++++++-
3 files changed, 234 insertions(+), 63 deletions(-)
--
2.26.2
next reply other threads:[~2021-01-20 10:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 10:40 Paolo Abeni [this message]
2021-01-20 10:40 ` [PATCH net-next 0/5] mptcp: re-enable sndbuf autotune Paolo Abeni
-- strict thread matches above, loose matches on Subject: below --
2021-01-20 10:40 [MPTCP] [PATCH net-next 1/5] mptcp: always graft subflow socket to parent Paolo Abeni
2021-01-20 10:40 ` Paolo Abeni
2021-01-20 10:40 [MPTCP] [PATCH net-next 2/5] mptcp: re-enable sndbuf autotune Paolo Abeni
2021-01-20 10:40 ` Paolo Abeni
2021-01-20 10:40 [MPTCP] [PATCH net-next 3/5] mptcp: do not queue excessive data on subflows Paolo Abeni
2021-01-20 10:40 ` Paolo Abeni
2021-01-20 10:40 [MPTCP] [PATCH net-next 4/5] mptcp: schedule work for better snd subflow selection Paolo Abeni
2021-01-20 10:40 ` Paolo Abeni
2021-01-20 10:40 [MPTCP] [PATCH net-next 5/5] mptcp: implement delegated actions Paolo Abeni
2021-01-20 10:40 ` Paolo Abeni
2021-01-20 12:48 [MPTCP] " Paolo Abeni
2021-01-20 12:48 ` 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=cover.1610991949.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.