netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Gilad Ben-Yossef <gilad@codefidence.com>
Cc: netdev@vger.kernel.org, ori@comsleep.com, ilpo.jarvinen@helsinki.fi
Subject: Re: [PATCHv3] IPv4 TCP fails to send window scale option when window scale is zero
Date: Thu, 01 Oct 2009 19:20:33 +0200	[thread overview]
Message-ID: <4AC4E4E1.5010300@gmail.com> (raw)
In-Reply-To: <1254413613.665110.11357.nullmailer@tron.codefidence.com>

Gilad Ben-Yossef a écrit :
> From: Ori Finkelman <ori@comsleep.com>
> 
> Acknowledge TCP window scale support by inserting the proper option in SYN/ACK 
> and SYN headers even if our window scale is zero.
> 
> This fixes the following observed behavior:
> 
> 1. Client sends a SYN with TCP window scaling option and non zero window scale 
> value to a Linux box.
> 2. Linux box notes large receive window from client.
> 3. Linux decides on a zero value of window scale for its part.
> 4. Due to compare against requested window scale size option, Linux does not to
>  send windows scale TCP option header on SYN/ACK at all.
> 
> With the following result:
> 
> Client box thinks TCP window scaling is not supported, since SYN/ACK had no 
> TCP window scale option, while Linux thinks that TCP window scaling is 
> supported (and scale might be non zero), since SYN had  TCP window scale 
> option and we have a mismatched idea between the client and server 
> regarding window sizes.
> 
> Probably it also fixes up the following bug (not observed in practice):
> 
> 1. Linux box opens TCP connection to some server.
> 2. Linux decides on zero value of window scale.
> 3. Due to compare against computed window scale size option, Linux does 
> not to set windows scale TCP  option header on SYN. 
> 
> With the expected result that the server OS does not use window scale option 
> due to not receiving such an option in the SYN headers, leading to suboptimal 
> performance.
> 
> Signed-off-by: Gilad Ben-Yossef <gilad@codefidence.com>
> Signed-off-by: Ori Finkelman <ori@comsleep.com>

Acked-by: Eric Dumazet <eric.dumazet@gmail.com>

Note, to reproduce the wscale set to 0 on active connections,
you have to play with /proc/sys/net settings :

echo 65535 >/proc/sys/net/core/rmem_max
echo "4096 16384 32768" >/proc/sys/net/ipv4/tcp_rmem

-> wscale 0 -> SYN packet without WSCALE option (on non patched kernels)


  reply	other threads:[~2009-10-01 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 16:13 [PATCHv3] IPv4 TCP fails to send window scale option when window scale is zero Gilad Ben-Yossef
2009-10-01 17:20 ` Eric Dumazet [this message]
2009-10-01 22:17   ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2009-10-01 16:24 Gilad Ben-Yossef
2009-10-01 16:41 Gilad Ben-Yossef

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=4AC4E4E1.5010300@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=gilad@codefidence.com \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=netdev@vger.kernel.org \
    --cc=ori@comsleep.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).