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: Wed, 17 Aug 2016 15:42:34 +0800 [thread overview]
Message-ID: <375f06dd-8439-bba3-8b45-781e1e48dc9c@intel.com> (raw)
In-Reply-To: <CADvbK_dKLU07+tW4f2XpCWgQME8mnjg8EObcfmH4i8s8Aume4w@mail.gmail.com>
On 08/17/2016 03:35 PM, Xin Long wrote:
>> include/net/sctp/structs.h | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
>> index d8e464aacb20..932f2780d3a4 100644
>> --- a/include/net/sctp/structs.h
>> +++ b/include/net/sctp/structs.h
>> @@ -602,6 +602,9 @@ struct sctp_chunk {
>> /* This needs to be recoverable for SCTP_SEND_FAILED events. */
>> struct sctp_sndrcvinfo sinfo;
>>
>> + unsigned long prsctp_param;
>> + int sent_count;
>> +
>> /* Which association does this belong to? */
>> struct sctp_association *asoc;
>>
>> --
>> 2.5.5
>>
>> Then the performance dropped to the same as the bisected commit
>> a6c2f792873a:
>> $ cat 4.7.0-rc6-01198-g98dd2532b14e/0/netperf.json
>> {
>> "netperf.Throughput_Mbps": [
>> 754.494375
>> ]
>> }
>>
>> I think this agrees with the perf data in that the newly added function
>> doesn't show up in the perf-profile but still, the performance drops.
>> So the only possible reason is the newly added fields to the sctp_chunk
>> structure.
>>
>> Is this expected?
> interesting , you didn't include the modification of the functions
> parts, right ?
Yes.
> you mean only this two line:
>> + unsigned long prsctp_param;
>> + int sent_count;ca;
>
> caused the performance issue ?
Right.
next prev parent reply other threads:[~2016-08-17 7:43 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
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 [this message]
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=375f06dd-8439-bba3-8b45-781e1e48dc9c@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
all inboxes | Powered by JetHome®