All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Paolo Abeni <pabeni@redhat.com>,
	Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH v2 mptcp-next] selftests: mptcp: fix diag instability
Date: Sat, 5 Feb 2022 11:32:55 +0100	[thread overview]
Message-ID: <002dc530-4938-725b-37ac-f46b6d8ae7ec@tessares.net> (raw)
In-Reply-To: <db50196c67b30e7b89d241faffc78e5ffbb04e83.1643976999.git.pabeni@redhat.com>

Hi Paolo, Mat,

On 04/02/2022 13:17, Paolo Abeni wrote:
> Instead of waiting for an arbitrary amount of time for the MPTCP
> MP_CAPABLE handshake to complete, explicitly wait for the relevant
> socket to enter into the established status.
> 
> Additionally let the data transfer application use the slowest
> transfer mode available (-r), to cope with very slow host, or
> high jitter caused by hosting VMs.

Thank you for the patch and the review!

Now in our tree (fixes for -net) with Closes, Fixes, my R&Tb and Mat's
RvB tags:

- 3b63b1552ae2: selftests: mptcp: fix diag instability

- Results: 4514f808428c..3150c57070f7

Builds and tests are now in progress:



https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20220205T103236

https://github.com/multipath-tcp/mptcp_net-next/actions/workflows/build-validation.yml?query=branch:export

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

      parent reply	other threads:[~2022-02-05 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 12:17 [PATCH v2 mptcp-next] selftests: mptcp: fix diag instability Paolo Abeni
2022-02-04 15:53 ` Matthieu Baerts
2022-02-04 18:32   ` Paolo Abeni
2022-02-04 20:52     ` Matthieu Baerts
2022-02-04 22:57       ` Mat Martineau
2022-02-05 10:32 ` Matthieu Baerts [this message]

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=002dc530-4938-725b-37ac-f46b6d8ae7ec@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.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.