linux-kernel - Re: [lkp] [sctp] a6c2f79287: netperf.Throughput

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Jul 2016 15:01:36 +0800
From:	Xin Long <lucien.xin@...il.com>
To:	kernel test robot <xiaolong.ye@...el.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>, lkp@...org
Subject: Re: [lkp] [sctp] a6c2f79287: netperf.Throughput_Mbps -37.2% regression

On Wed, Jul 27, 2016 at 9:54 AM, kernel test robot
<xiaolong.ye@...el.com> wrote:
>
> FYI, we noticed a -37.2% regression of netperf.Throughput_Mbps due to commit:
>
> commit a6c2f792873aff332a4689717c3cd6104f46684c ("sctp: implement prsctp TTL policy")
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> in testcase: netperf
> on test machine: 4 threads Ivy Bridge with 8G memory
> with following parameters:
>
>         ip: ipv4
>         runtime: 300s
>         nr_threads: 200%
>         cluster: cs-localhost
>         send_size: 10K
>         test: SCTP_STREAM_MANY
>         cpufreq_governor: performance
>
>
>
> Disclaimer:
> Results have been estimated based on internal Intel analysis and are provided
> for informational purposes only. Any difference in system hardware or software
> design or configuration may affect actual performance.
>
It doesn't make much sense to me. the codes I added cannot be
triggered without enable any pr policies. and I also did the tests in
my local environment,  the result looks normal to me compare to
prior version.

Recently the sctp performance is not stable,  as during these patches,
netperf cannot get the result, but return ENOTCONN. which may
also affect the testing. anyway we've fixed the -ENOTCONN issue
already in the latest version.