From: "Alex,Shi" <alex.shi@intel.com>
To: davem@davemloft.net
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tim Chen <tim.c.chen@intel.com>,
"Huang, Ying" <ying.huang@intel.com>
Subject: TCP_STREAM performance regression on commit b3613118
Date: Fri, 17 Feb 2012 16:18:14 +0800 [thread overview]
Message-ID: <1329466694.12669.2976.camel@debian> (raw)
The tcp_stream loop back performance has about 10% drop on the
commitment on our core2 2 sockets server. This commit has 2
parents(7505afe28, 5983fe), but both of them have no regression. So
guess the impact just happened when this 2 parents joint. That beyond
our capability to dig it more.
Any ideas?
Regards!
Alex
next reply other threads:[~2012-02-17 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 8:18 Alex,Shi [this message]
2012-02-17 9:50 ` TCP_STREAM performance regression on commit b3613118 Eric Dumazet
2012-02-17 18:33 ` David Miller
2012-02-20 1:44 ` Alex,Shi
2012-03-02 2:45 ` Alex Shi
2012-03-02 3:07 ` David Miller
2012-03-02 6:37 ` Alex Shi
2012-03-02 12:28 ` Eric Dumazet
2012-03-06 8:11 ` Feng Tang
2012-03-06 8:26 ` Jason Wang
2012-03-06 12:01 ` Eric Dumazet
2012-03-07 2:55 ` Feng Tang
2012-03-06 18:23 ` Rick Jones
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=1329466694.12669.2976.camel@debian \
--to=alex.shi@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@intel.com \
--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