netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: bert hubert <ahu@ds9a.nl>
Cc: jamie@shareable.org, shemminger@osdl.org, netdev@oss.sgi.com,
	linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix tcp_default_win_scale.
Date: Tue, 6 Jul 2004 15:49:07 -0700	[thread overview]
Message-ID: <20040706154907.422a6b73.davem@redhat.com> (raw)
In-Reply-To: <20040706224453.GA6694@outpost.ds9a.nl>

On Wed, 7 Jul 2004 00:44:53 +0200
bert hubert <ahu@ds9a.nl> wrote:

> Not true - the outgoing SYN packet had window scale 7, when it was sent. The
> SYN|ACK had window scale 0, when received by the initiating system.
> 
> Also - even if the remote were to assume a 47 byte window size, would it not
> be able to send small packets? Or does the window size also include
> packet haders?

SWS avoidance makes us not send packets.  See this quote in an email
from John Heffner the other week:

================================
To elaborate on my earlier mail. my hypothesis is that somehow the web
server beleives that we sent a winscale of 0.  In such a case, when we try
to advertise our initial 4*MSS (5840 bytes) of window, with a window scale
of 3 we use a value of 730 in the window field.  All sender SWS avoidance
(RFC1122) tests will fail, most notably 1 (because we already advertised
5840 bytes and 730 < 5840/2) and 3 (because 730 < 1460).  With a winscale
of 2, we will use a value of 1460 in the window field, so both tests will
succeed.
================================

  reply	other threads:[~2004-07-06 22:49 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <32886.63.170.215.71.1088564087.squirrel@www.osdl.org>
     [not found] ` <20040629222751.392f0a82.davem@redhat.com>
     [not found]   ` <20040630152750.2d01ca51@dell_ss3.pdx.osdl.net>
     [not found]     ` <20040630153049.3ca25b76.davem@redhat.com>
2004-07-01 20:37       ` [PATCH] TCP acts like it is always out of memory Stephen Hemminger
2004-07-01 21:04         ` David S. Miller
2004-07-02  1:32           ` Arnaldo Carvalho de Melo
2004-07-06  9:35             ` analysis of TCP window size issues still around - several reports / SACK involved? bert hubert
2004-07-06 18:47               ` [PATCH] fix tcp_default_win_scale Stephen Hemminger
2004-07-06 19:40                 ` Jamie Lokier
2004-07-06 20:05                   ` Stephen Hemminger
2004-07-06 20:28                     ` David S. Miller
2004-07-06 20:36                       ` Stephen Hemminger
2004-07-06 20:35                         ` David S. Miller
2004-07-06 21:55                           ` John Heffner
2004-07-06 22:50                             ` David S. Miller
2004-07-07  1:32                               ` John Heffner
2004-07-06 23:01                           ` PLS help fix: recent 2.6.7 won't connect to anything " bert hubert
2004-07-06 20:12                   ` David S. Miller
2004-07-06 22:44                     ` bert hubert
2004-07-06 22:49                       ` David S. Miller [this message]
2004-07-07 18:06                         ` Stephen Hemminger
2004-07-07 19:31                           ` Jamie Lokier
2004-07-07 19:38                             ` bert hubert
2004-07-07 19:41                           ` John Heffner
2004-07-09 23:14                           ` David S. Miller
2004-07-06 20:00                 ` Nivedita Singhvi
2004-07-06 20:16                   ` David S. Miller
2004-07-06 20:26                     ` David Ford
     [not found]                 ` <20040706185856.GN18841@lug-owl.de>
2004-07-06 20:17                   ` David S. Miller
2004-07-06 20:31                     ` Stephen Hemminger
2004-07-06 20:33                       ` David S. Miller
2004-07-06 20:24                 ` David S. Miller
2004-07-06 23:16                   ` Andi Kleen
2004-07-07  7:50                     ` Chris Wedgwood
2004-07-06 23:19                 ` Redeeman
2004-07-07 19:47                 ` John Heffner
2004-07-06 20:19               ` analysis of TCP window size issues still around - several reports / SACK involved? David S. Miller
2004-07-06 20:27                 ` bert hubert
2004-07-06 20:31                   ` David S. Miller
2004-07-07 21:25                   ` Alessandro Suardi
2004-07-06 20:35 [PATCH] fix tcp_default_win_scale Tim Berti
2004-07-06 20:54 ` David Ford

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=20040706154907.422a6b73.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ahu@ds9a.nl \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.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).