[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160819072420.GA1167@aaronlu.sh.intel.com>
Date: Fri, 19 Aug 2016 15:24:20 +0800
From: Aaron Lu <aaron.lu@...el.com>
To: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
Cc: Xin Long <lucien.xin@...il.com>,
kernel test robot <xiaolong.ye@...el.com>,
Stephen Rothwell <sfr@...b.auug.org.au>, lkp@...org,
"David S. Miller" <davem@...emloft.net>,
LKML <linux-kernel@...r.kernel.org>,
"Chen, Tim C" <tim.c.chen@...el.com>,
Huang Ying <ying.huang@...el.com>
Subject: Re: [LKP] [lkp] [sctp] a6c2f79287: netperf.Throughput_Mbps -37.2%
regression
On Fri, Aug 19, 2016 at 04:19:39AM -0300, Marcelo Ricardo Leitner wrote:
> Hi,
>
> Em 19-08-2016 02:29, Aaron Lu escreveu:
> ...
> > It doesn't look insane and sctp_wait_for_sndbuf may actually have
> > something to do with a larger sctp_chunk I suppose?
> >
> > The same perf record doesn't capture any sample for the good commit,
> > which suggests the nerperf process doesn't sleep in sctp_wait_for_sndbuf.
>
> Ahhh yes! It does, and then it would mean your txbuf is too small for the
> chunk sizes you're using (sctp tests option -m).
>
> What's your netperf cmdline again please?
netperf -4 -t SCTP_STREAM_MANY -c -C -l 300 -- -m 10K -H 127.0.0.1
Is the 10K used here a problem? If so, can you suggest a proper value
for our netperf performance test? Thanks.
Regards,
Aaron
Powered by blists - more mailing lists