MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v3 mptcp-next 0/4] mptcp: re-enable snd buf autotune
Date: Tue, 12 Jan 2021 16:23:05 -0800	[thread overview]
Message-ID: <c5decfac-eca2-2a9b-7976-528aa728748f@linux.intel.com> (raw)
In-Reply-To: cover.1610449705.git.pabeni@redhat.com

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]


On Tue, 12 Jan 2021, Paolo Abeni wrote:

> WRT to the previous iteration, this clean-up patch 2/4 dropping the
> left over 'use_backup' field, as suggested by Mat. No other change
>
> Relevant bits from the previous cover letter:
>
> There are still some sporadic self-test failures for assimetric links.
> Looks like they are caused by retransmissions/receiver dropping packets
> due to MPTCP level OoO check.
>
> I'll try to address that asap, but I still consider this series for
> inclusion, so that it can stage a bit in the export branch.
>
> Note: the last patch re-introduces the workqueue usage for the datapath (yes,
> it makes me feel sick, sad and tired :(. I was unable to avoid it.
>
>
> Paolo Abeni (4):
>  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
>
> net/mptcp/protocol.c | 104 +++++++++++++++++--------------------------
> net/mptcp/protocol.h |  20 +++++++++
> net/mptcp/subflow.c  |  13 +++++-
> 3 files changed, 73 insertions(+), 64 deletions(-)
>
> -- 
> 2.26.2

Thanks Paolo. I think v3 of the series looks good to stage on the export 
branch.

--
Mat Martineau
Intel

             reply	other threads:[~2021-01-13  0:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13  0:23 Mat Martineau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-13 18:05 [MPTCP] Re: [PATCH v3 mptcp-next 0/4] mptcp: re-enable snd buf autotune 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=c5decfac-eca2-2a9b-7976-528aa728748f@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