From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp-next v2] selftests: mptcp: add link failure test case
Date: Sat, 17 Oct 2020 09:31:30 +0200 [thread overview]
Message-ID: <f41520c0-1cbb-8251-22d7-96b36643095f@tessares.net> (raw)
In-Reply-To: d44679b6-8aa0-a1f9-19b9-4713495de53@linux.intel.com
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Hi Florian, Mat,
On 15/10/2020 02:09, Mat Martineau wrote:
> On Fri, 9 Oct 2020, Florian Westphal wrote:
>
>> Add a test case where a link fails with multiple subflows.
>> The expectation is that MPTCP will transmit any data that
>> could not be delivered via the failed link on another subflow.
>>
>> Signed-off-by: Florian Westphal <fw(a)strlen.de>
>> ---
>> v2: rebase and add 'link loss' to test-case comment.
>> make sure we exit with 1 if file was corrupt or server/client
>> exited nonzero.
>>
>> .../testing/selftests/net/mptcp/mptcp_join.sh | 135 +++++++++++++-----
>> 1 file changed, 97 insertions(+), 38 deletions(-)
>>
>
> Thanks for the v2, looks good for the export branch.
Thank you for the patch and the review!
Just applied with Mat's Reviewed-by.
- 36221baa8712: selftests: mptcp: add link failure test case
- Results: 3fd01a5ab17b..0e70ef7be280
Tests and export will be started soon!
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
next reply other threads:[~2020-10-17 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 7:31 Matthieu Baerts [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-24 12:17 [MPTCP] Re: [PATCH mptcp-next v2] selftests: mptcp: add link failure test case Florian Westphal
2020-10-24 10:05 Matthieu Baerts
2020-10-15 0:09 Mat Martineau
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=f41520c0-1cbb-8251-22d7-96b36643095f@tessares.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.