From: "David S. Miller" <davem@davemloft.net>
To: "Scott M. Ferris" <sferris@acm.org>
Cc: netdev@oss.sgi.com
Subject: Re: TSO prevents cwnd growth on 2.6 kernels
Date: Fri, 25 Mar 2005 10:40:00 -0800 [thread overview]
Message-ID: <20050325104000.713229be.davem@davemloft.net> (raw)
In-Reply-To: <20050325181804.GA11633@visi.com>
On Fri, 25 Mar 2005 12:18:04 -0600
"Scott M. Ferris" <sferris@acm.org> wrote:
> TSO still has problems in 2.6.12-rc1.
We know it's busted. I haven't gotten to fixing this stuff
up yet.
> tcp_write_xmit() really needs to be willing to increase
> tcp_packets_in_flight() high enough that tcp_ack() will allow the
> congestion window to grow, even when TSO is being used, otherwise
> there may be a dramatic reduction in the cwnd growth rate.
Are you suggesting to let it go past tp->snd_cwnd? We can't
ever do that. tp->snd_cwnd is a hard limit on the number
of frames we may have outstanding on the network at one time,
TSO or not.
next prev parent reply other threads:[~2005-03-25 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 18:18 TSO prevents cwnd growth on 2.6 kernels Scott M. Ferris
2005-03-25 18:40 ` David S. Miller [this message]
2005-03-25 19:34 ` Scott M. Ferris
2005-03-25 19:40 ` David S. Miller
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=20050325104000.713229be.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=sferris@acm.org \
/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).