From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: alex.shi@intel.com, linux-kernel@vger.kernel.org,
tim.c.chen@intel.com, ying.huang@intel.com,
netdev@vger.kernel.org
Subject: Re: TCP_STREAM performance regression on commit b3613118
Date: Fri, 17 Feb 2012 13:33:27 -0500 (EST) [thread overview]
Message-ID: <20120217.133327.1178765872497293871.davem@davemloft.net> (raw)
In-Reply-To: <1329472239.2861.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 17 Feb 2012 10:50:39 +0100
> Le vendredi 17 février 2012 à 16:18 +0800, Alex,Shi a écrit :
>> 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?
>
> Most probably the more accurate truesize determination is responsible of
> this tcp regression, since some prior assumptions might be wrong.
>
> Want to give more information on the workload ?
> Is it a 32 or 64 bit kernel ?
And let's start CC:'ing netdev too.
next parent reply other threads:[~2012-02-17 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329466694.12669.2976.camel@debian>
[not found] ` <1329472239.2861.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
2012-02-17 18:33 ` David Miller [this message]
2012-02-20 1:44 ` TCP_STREAM performance regression on commit b3613118 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=20120217.133327.1178765872497293871.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.shi@intel.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).