From: "Huang\, Ying" <ying.huang@linux.intel.com>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: Huang Ying <ying.huang@intel.com>, <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [lkp] [net] 192132b9a0: -17.5% netperf.Throughput_tps
Date: Tue, 29 Sep 2015 16:45:41 +0800 [thread overview]
Message-ID: <87h9mdlikq.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <56036A05.8000805@cumulusnetworks.com> (David Ahern's message of "Wed, 23 Sep 2015 21:12:05 -0600")
David Ahern <dsa@cumulusnetworks.com> writes:
> On 9/23/15 6:37 PM, Huang Ying wrote:
>>>
>>> I take it you have CONFIG_NET_VRF enabled. correct?
>>>
>>> With it disabled I see no relevant change in performance between
>>> 8f58336d3f78 and 192132b9a034. Can you confirm?
>>
>> The kconfig file is attached with the mail. It appears that
>> CONFIG_NET_VRF is disabled.
>>
>
> Something is not adding up. I anticipate access to a multi-socket numa
> system in the next few days. Until then a couple of questions:
>
> 1. do you take patches to run your tests?
No. We checkout your commits and test them. Without applying any other patches.
> 2. do you have a wiki/web page with all of the tests run?
Sorry, we still have no this information now.
> I'd like to
> know what other networking tests have been run. Only this one was
> flagged, so I presume it means other tests did not hit the
> threshold. I would like to know what other tests are run.
For the commit and its parent, we have only tested the benchmark in the
report email.
Best Regards,
Huang, Ying
prev parent reply other threads:[~2015-09-29 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eghtb7e8.fsf@yhuang-dev.intel.com>
2015-09-21 1:19 ` [lkp] [net] 192132b9a0: -17.5% netperf.Throughput_tps David Ahern
2015-09-21 1:33 ` Huang Ying
2015-09-21 3:48 ` David Ahern
2015-09-23 18:06 ` David Ahern
2015-09-24 0:37 ` Huang Ying
2015-09-24 3:12 ` David Ahern
2015-09-29 8:45 ` Huang, Ying [this message]
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=87h9mdlikq.fsf@yhuang-dev.intel.com \
--to=ying.huang@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@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