netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@intel.com>
To: David Miller <davem@davemloft.net>
Cc: feng.tang@intel.com, 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 14:37:57 +0800	[thread overview]
Message-ID: <1330670277.21053.1448.camel@debian> (raw)
In-Reply-To: <20120301.220743.2174015405223036036.davem@davemloft.net>

On Thu, 2012-03-01 at 22:07 -0500, David Miller wrote:
> From: Alex Shi <alex.shi@intel.com>
> Date: Fri, 02 Mar 2012 10:45:17 +0800
> 
> > Add CC to tang feng, He is working on this issue. 
> 
> Is he?  I'm pretty sure this is due to the TCP receive window growing
> issue Eric Dumazet, Neal Cardwell and I are discussing in the thread
> starting at:
> 
> http://marc.info/?l=linux-netdev&m=132916352815286&w=2

That's great! 
May my language make you confusing. Actually, Feng is doing
investigation on this issue. Since you fund out the reason, it saved his
work. :) 

  reply	other threads:[~2012-03-02  6:37 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   ` TCP_STREAM performance regression on commit b3613118 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 [this message]
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=1330670277.21053.1448.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 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).