linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <edumazet@google.com>
To: rong.a.chen@intel.com
Cc: Yuchung Cheng <ycheng@google.com>,
	David Miller <davem@davemloft.net>, Wei Wang <weiwan@google.com>,
	Neal Cardwell <ncardwell@google.com>,
	Soheil Hassas Yeganeh <soheil@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [LKP] [tcp] a337531b94: netperf.Throughput_Mbps -6.1% regression
Date: Tue, 9 Oct 2018 19:05:20 -0700	[thread overview]
Message-ID: <CANn89i+RDyhy9k22GHpJVzOWzCK3Hd6z89bABWDXmsgc6w+h9g@mail.gmail.com> (raw)
In-Reply-To: <20181010015143.GD13396@shao2-debian>

On Tue, Oct 9, 2018 at 7:01 PM kernel test robot <rong.a.chen@intel.com> wrote:
>
> Greeting,
>
> FYI, we noticed a -6.1% regression of netperf.Throughput_Mbps due to commit:
>
>
> commit: a337531b942bd8a03e7052444d7e36972aac2d92 ("tcp: up initial rmem to 128KB and SYN rwin to around 64KB")
> https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git master
>
> in testcase: netperf
> on test machine: 16 threads Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz with 8G memory
> with following parameters:
>
>         ip: ipv4
>         runtime: 900s
>         nr_threads: 200%
>         cluster: cs-localhost
>         test: TCP_STREAM
>         ucode: 0x7000013
>         cpufreq_governor: performance
>
> test-description: Netperf is a benchmark that can be use to measure various aspect of networking performance.
> test-url: http://www.netperf.org/netperf/
>
>

This should have been fixed by :

041a14d2671573611ffd6412bc16e2f64469f7fb tcp: start receiver buffer
autotuning sooner

  reply	other threads:[~2018-10-10  2:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10  1:51 [LKP] [tcp] a337531b94: netperf.Throughput_Mbps -6.1% regression kernel test robot
2018-10-10  2:05 ` Eric Dumazet [this message]
2018-10-24 12:13 kernel test robot
2018-10-24 13:27 ` Eric Dumazet
2018-10-28  1:43   ` Wang, Kemi

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=CANn89i+RDyhy9k22GHpJVzOWzCK3Hd6z89bABWDXmsgc6w+h9g@mail.gmail.com \
    --to=edumazet@google.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=rong.a.chen@intel.com \
    --cc=soheil@google.com \
    --cc=weiwan@google.com \
    --cc=ycheng@google.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;
as well as URLs for NNTP newsgroup(s).