From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp-next] mptcp: push pending frames when subflow has free space
Date: Wed, 09 Dec 2020 17:42:04 -0800 [thread overview]
Message-ID: <306ee763-731-c88c-97f0-b9fb28f8a31d@linux.intel.com> (raw)
In-Reply-To: 41eec9f439fdbe2ae5549f6222af4b24f58c0af5.1607535998.git.pabeni@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Wed, 9 Dec 2020, Paolo Abeni wrote:
> When multiple subflows are active, we can receive a
> window update on subflow with no write space available.
> MPTCP will try to push frames on such subflow and will
> fail. Pending frames will be pushed only after receiving
> a window update on a subflow with some wspace available.
>
> Overall the above could lead to suboptimal aggregate
> bandwidth usage.
>
> Instead, we should try to push pending frames as soon as
> the subflow reaches both conditions mentioned above.
>
> We can finally enable self-tests with asymmetric links,
> as the above makes them finally pass.
>
> Signed-off-by: Paolo Abeni <pabeni(a)redhat.com>
> ---
> net/mptcp/options.c | 13 ++++++++-----
> net/mptcp/protocol.c | 2 +-
> net/mptcp/protocol.h | 2 +-
> tools/testing/selftests/net/mptcp/simult_flows.sh | 6 +++---
> 4 files changed, 13 insertions(+), 10 deletions(-)
Hi Paolo -
Looks good!
Reviewed-by: Mat Martineau <mathew.j.martineau(a)linux.intel.com>
--
Mat Martineau
Intel
next reply other threads:[~2020-12-10 1:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 1:42 Mat Martineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-10 9:54 [MPTCP] Re: [PATCH mptcp-next] mptcp: push pending frames when subflow has free space Matthieu Baerts
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=306ee763-731-c88c-97f0-b9fb28f8a31d@linux.intel.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox