mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: kernel test robot <xiaolong.ye@intel.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	lkp@01.org, "David S. Miller" <davem@davemloft.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [sctp] a6c2f79287: netperf.Throughput_Mbps -37.2% regression
Date: Tue, 16 Aug 2016 16:30:43 +0800	[thread overview]
Message-ID: <614ad3e6-b231-92da-1d28-9ad3faec691a@intel.com> (raw)
In-Reply-To: <CADvbK_cy+EW228-_R9rDu2Bkt2VSNmVwCYsHEv6KPB8YarNRiA@mail.gmail.com>

On 08/16/2016 04:02 PM, Xin Long wrote:
>>
>> I'm testing on Linus' master, can we all use that please?
>>
> 
> [git] git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> 
> [mechine]
> Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
> mem 62G (66000220K)
> 
> [system]
> # cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 7.3 Beta (Maipo)
> 
> [commit 3684b03]
> [root@hp-dl380pg8-11 lxin]# uname -r
> 4.8.0-rc2.3684b03
> [root@hp-dl380pg8-11 lxin]# cat test.sh
> killall -0 netserver || netserver -4 &
> netperf -4 -t SCTP_STREAM_MANY -c -C -l 300 -- -m 10K -H 127.0.0.1
> [root@hp-dl380pg8-11 lxin]# sh test.sh
> SCTP 1-TO-MANY STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
> 127.0.0.1 () port 0 AF_INET
> Recv   Send    Send                          Utilization       Service Demand
> Socket Socket  Message  Elapsed              Send     Recv     Send    Recv
> Size   Size    Size     Time     Throughput  local    remote   local   remote
> bytes  bytes   bytes    secs.    10^6bits/s  % S      % S      us/KB   us/KB
> 
> 212992 212992  10240    300.00     16914.99   3.28     3.28     0.636   0.636
> 
> [commit f959fb4]
> [root@localhost lxin]# uname -r
> 4.7.0-rc6.f959fb4
> [root@localhost lxin]# cat test.sh
> killall -0 netserver || netserver -4 &
> netperf -4 -t SCTP_STREAM_MANY -c -C -l 300 -- -m 10K -H 127.0.0.1
> [root@localhost lxin]# sh test.sh
> SCTP 1-TO-MANY STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
> 127.0.0.1 () port 0 AF_INET
> Recv   Send    Send                          Utilization       Service Demand
> Socket Socket  Message  Elapsed              Send     Recv     Send    Recv
> Size   Size    Size     Time     Throughput  local    remote   local   remote
> bytes  bytes   bytes    secs.    10^6bits/s  % S      % S      us/KB   us/KB
> 
> 212992 212992  10240    300.00     12975.32   3.35     3.35     0.847   0.846
> 
> 
> Still, in my env, the latest kernel is better than old one.
> Sorry, I'm not sure why it's so different in your env.

Could the test have anything to do with the hardware? i.e. yours is Xeon
E5-2690 while mine is IVB i3?

> 
> Could you do 'netperf' test manually, instead of lkp-tests, then check again.

Manually test under LKP is not easy as those test machines are all doing
things automatically. But if you think that is necessary, I can do that.

> Pls show you system's distros as well, like rhel, ubuntu or arch ?

We do not use any of these distros.
The rootfs is derived from debian:
https://github.com/fengguang/reproduce-kernel-bug/blob/master/debian/debian-x86_64-2015-02-07.cgz

Thanks,
Aaron

  reply	other threads:[~2016-08-16  8:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  1:54 kernel test robot
2016-07-28  7:01 ` Xin Long
2016-08-05  3:31   ` [LKP] " Aaron Lu
2016-08-05 11:53     ` Xin Long
2016-08-08  2:10       ` Aaron Lu
2016-08-16  2:38         ` Aaron Lu
2016-08-16  8:02         ` Xin Long
2016-08-16  8:30           ` Aaron Lu [this message]
2016-08-16  8:51           ` Aaron Lu
2016-08-16  9:56             ` Xin Long
2016-08-17  5:04               ` Aaron Lu
2016-08-17  5:34                 ` Xin Long
2016-08-17  5:34                 ` Aaron Lu
2016-08-17  5:41                   ` Xin Long
2016-08-17  6:14                     ` Aaron Lu
2016-08-17  6:37                       ` Aaron Lu
2016-08-17  6:42                         ` Aaron Lu
2016-08-17  7:35                         ` Xin Long
2016-08-17  7:42                           ` Aaron Lu
2016-08-17  7:53                             ` Aaron Lu
2016-08-17  8:02                             ` Xin Long
2016-08-17  8:48                               ` Aaron Lu
2016-08-17  8:58                                 ` Xin Long
2016-08-17  9:20                                   ` Aaron Lu
2016-08-17 18:06                                     ` Xin Long
2016-08-18  3:21                                       ` Aaron Lu
2016-08-18 12:45                                         ` Xin Long
2016-08-19  5:29                                           ` Aaron Lu
2016-08-19  7:19                                             ` Marcelo Ricardo Leitner
2016-08-19  7:24                                               ` Aaron Lu
2016-08-22 21:44                                                 ` Marcelo Ricardo Leitner
2016-08-23  9:19                                                   ` Aaron Lu
2016-09-30  7:05                                                   ` Aaron Lu
2016-10-03  2:32                                                     ` Xin Long
2016-10-09  7:41                                                       ` Aaron Lu
2016-08-16 18:34             ` Xin Long

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=614ad3e6-b231-92da-1d28-9ad3faec691a@intel.com \
    --to=aaron.lu@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=lucien.xin@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=xiaolong.ye@intel.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

Powered by JetHome