From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliangtang@gmail.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
Geliang Tang <geliang.tang@suse.com>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next] Squash to "selftests: mptcp: add MP_FAIL reset testcase" - cleanups
Date: Wed, 4 May 2022 16:39:49 -0700 (PDT) [thread overview]
Message-ID: <978b9bb7-5a46-b756-288a-afc94ddda678@linux.intel.com> (raw)
In-Reply-To: <65c6e3d4-795a-17e0-8a2-337da6e6cfac@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]
On Wed, 4 May 2022, Mat Martineau wrote:
> On Wed, 4 May 2022, Geliang Tang wrote:
>
>> Paolo Abeni <pabeni@redhat.com> 于2022年5月4日周三 21:04写道:
>>>
>>> Hi Geliang,
>>>
>>> On Wed, 2022-05-04 at 20:14 +0800, Geliang Tang wrote:
>>>> On Wed, May 04, 2022 at 07:44:24PM +0800, Geliang Tang wrote:
>>>>> Two small cleanups for MP_FAIL reset test case:
>>>>>
>>>>> Reduce the test files size from 1024 to 128, to make the test faster.
>>>>
>>>> The original commit log needs to update too:
>>>>
>>>> 1024KB -> 128KB
>>>>
>>>> '''
>>>> Add the multiple subflows test case for MP_FAIL, to test the MP_FAIL
>>>> reset case. Use the test_linkfail value to make 128KB test files.
>>>>
>>>> ...
>>>> ...
>>>> '''
>>>>
>>>>> With Paolo's fix [2] for MP_FAIL test-case, the test becomes very slow.
>>>>>
>>>>> Drop '+'s passed to chk_csum_nr, with Paolo's fix [1] for act_pedit, no
>>>>> extra checksum failures now, no need to add '+'s anymore.
>>>>>
>>>>> Depends on Paolo's commits:
>>>>> [1] net/sched: act_pedit: really ensure the skb is writable
>>>>> [2] selftests: mptcp: fix MP_FAIL test-case
>>>>>
>>>>> Signed-off-by: Geliang Tang <geliang.tang@suse.com>
>>>
>>> I noticed the the time increase. Unfortunatelly, it may be necessary to
>>> be reliable in all environment, comprising the slowers one.
>>>
>>> Mat (M.) was able to reproduce some failure with b/w == 10Mbps and size
>>> == 1M. I think/guess he could hit the same failure even with 1Mbps and
>>> size == 128K.
>>>
>>> We need at least some additional testing for this one.
>>
>> If so, let's continue to use 1024k test file sizes.
>>
>
> It's reliable for me at 128k so far. I'm fine with squashing the patch as-is,
> we can increase the file size if CI (or humans) complain.
>
It did fail after 193 iterations (kernel with debug config):
002 MP_FAIL MP_RST: 1 corrupted pkts syn[ ok ] - synack[ ok ] - ack[ ok ]
sum[ ok ] - csum [ ok ]
ftx[ ok ] - failrx[fail] got 0 MP_FAIL[s] RX expected 1
So 128k seems to be too small.
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-05-04 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 11:44 [PATCH mptcp-next] Squash to "selftests: mptcp: add MP_FAIL reset testcase" - cleanups Geliang Tang
2022-05-04 11:51 ` Squash to "selftests: mptcp: add MP_FAIL reset testcase" - cleanups: Build Failure MPTCP CI
2022-05-04 12:14 ` [PATCH mptcp-next] Squash to "selftests: mptcp: add MP_FAIL reset testcase" - cleanups Geliang Tang
2022-05-04 13:03 ` Paolo Abeni
2022-05-04 13:08 ` Matthieu Baerts
2022-05-04 13:21 ` Geliang Tang
2022-05-04 23:00 ` Mat Martineau
2022-05-04 23:39 ` Mat Martineau [this message]
2022-05-04 12:21 ` Squash to "selftests: mptcp: add MP_FAIL reset testcase" - cleanups: Tests Results MPTCP CI
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=978b9bb7-5a46-b756-288a-afc94ddda678@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=geliang.tang@suse.com \
--cc=geliangtang@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox