From: rick jones <rick.jones2@hp.com>
To: netdev@oss.sgi.com
Cc: romieu@fr.zoreil.com, hubert.tonneau@fullpliant.org, shemminger@osdl.org
Subject: Re: 2.6.10 TCP troubles -- suggested patch
Date: Sat, 12 Feb 2005 17:29:16 -0800 [thread overview]
Message-ID: <67e9e71a41cc2a840cc89f836e2b6f4b@hp.com> (raw)
In-Reply-To: <20050212220010.GA29417@yakov.inr.ac.ru>
On Feb 12, 2005, at 2:00 PM, Alexey Kuznetsov wrote:
> Any which follows some of congestion window validation recommendations.
If you could point me at the chapter and verse that would be great.
> Even canonical bsd restarts slow start after rtt.
Did we have >= one RTT of idle in the packet trace?
>> N is something other than one though.
>
> Well, 1 is quite enough to be sure that something is very wrong.
> You see a proof here.
The debate of course is what :)
In and of _itself_, a delayed ACK does not guarantee something is very
wrong. For example, in a request/response situation when the response
takes longer than the delayed ACK interval to generate. And if it was
not request/response, and the sender simply didn't have any more to
send at that point.
Going back to the quantity of cwnd which may be left unused when TSO is
enabled. If when TSO is enabled, the sender does not take full
advantage of the cwnd doesn't that then mean that to deal with the same
bandwidth delay product, one needs a larger TCP window when TSO is
enabled than when it is not? In the default case of
tcp_tso_win_divisor being 8 that would be another 12.5% right?
rick jones
there is no rest for the wicked, yet the virtuous have no pillows
next prev parent reply other threads:[~2005-02-13 1:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 21:55 2.6.10 TCP troubles -- suggested patch Hubert Tonneau
2005-02-11 22:54 ` Rick Jones
2005-02-11 23:09 ` Nivedita Singhvi
2005-02-11 23:40 ` Rick Jones
2005-02-12 1:08 ` David S. Miller
2005-02-12 1:09 ` David S. Miller
2005-02-12 14:31 ` Alexey Kuznetsov
2005-02-12 19:28 ` David S. Miller
2005-02-12 19:44 ` Leonid Grossman
2005-02-12 19:52 ` Alexey Kuznetsov
2005-02-15 23:25 ` David S. Miller
2005-02-12 20:19 ` rick jones
2005-02-12 20:28 ` David S. Miller
2005-02-12 20:56 ` Alexey Kuznetsov
2005-02-12 21:27 ` Nivedita Singhvi
2005-02-12 21:43 ` rick jones
2005-02-12 22:00 ` Alexey Kuznetsov
2005-02-13 1:29 ` rick jones [this message]
2005-02-11 23:04 ` Stephen Hemminger
2005-02-12 1:07 ` David S. Miller
2005-02-12 12:11 ` Andi Kleen
2005-02-12 19:23 ` David S. Miller
2005-02-12 21:30 ` Andi Kleen
2005-02-12 14:16 ` Alexey Kuznetsov
2005-02-12 19:41 ` David S. Miller
2005-02-12 20:03 ` Alexey Kuznetsov
2005-02-15 23:26 ` David S. Miller
2005-02-15 23:42 ` Rick Jones
2005-02-15 23:23 ` David S. Miller
2005-02-16 9:13 ` Alexey Kuznetsov
2005-02-16 17:50 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2005-02-20 23:06 Hubert Tonneau
2005-02-16 20:00 Hubert Tonneau
2005-02-13 10:52 Hubert Tonneau
2005-02-14 14:12 ` Alexey Kuznetsov
2005-02-10 21:53 Hubert Tonneau
2005-02-10 22:36 ` Rick Jones
2005-02-11 1:16 ` David S. Miller
[not found] <050QTJA12@server5.heliogroup.fr>
2005-02-09 18:59 ` Stephen Hemminger
2005-02-09 20:25 ` 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=67e9e71a41cc2a840cc89f836e2b6f4b@hp.com \
--to=rick.jones2@hp.com \
--cc=hubert.tonneau@fullpliant.org \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@osdl.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).