On Wed, Jul 27, 2016 at 9:54 AM, kernel test robot
FYI, we noticed a -37.2% regression of netperf.Throughput_Mbps due to commit:
commit a6c2f792873aff332a4689717c3cd6104f46684c ("sctp: implement prsctp TTL
in testcase: netperf
on test machine: 4 threads Ivy Bridge with 8G memory
with following parameters:
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
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.