From: Alex Shi <alex.shi@intel.com>
To: David Miller <davem@davemloft.net>, Tang Feng <feng.tang@intel.com>
Cc: eric.dumazet@gmail.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, 02 Mar 2012 10:45:17 +0800 [thread overview]
Message-ID: <1330656317.21053.1411.camel@debian> (raw)
In-Reply-To: <20120217.133327.1178765872497293871.davem@davemloft.net>
On Fri, 2012-02-17 at 13:33 -0500, David Miller wrote:
> 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.
Add CC to tang feng, He is working on this issue.
next prev parent reply other threads:[~2012-03-02 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 8:18 TCP_STREAM performance regression on commit b3613118 Alex,Shi
2012-02-17 9:50 ` Eric Dumazet
2012-02-17 18:33 ` David Miller
2012-02-20 1:44 ` Alex,Shi
2012-03-02 2:45 ` Alex Shi [this message]
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=1330656317.21053.1411.camel@debian \
--to=alex.shi@intel.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=feng.tang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.