Re: [tcpm] Increasing the Initial Window - Notes

rick jones <perfgeek@mac.com> Wed, 10 November 2010 17:20 UTC

Return-Path: <perfgeek@mac.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 882C63A697F for <tcpm@core3.amsl.com>; Wed, 10 Nov 2010 09:20:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CRrCHHWNJlF7 for <tcpm@core3.amsl.com>; Wed, 10 Nov 2010 09:19:59 -0800 (PST)
Received: from asmtpout016.mac.com (asmtpout016.mac.com [17.148.16.91]) by core3.amsl.com (Postfix) with ESMTP id BC1593A6956 for <tcpm@ietf.org>; Wed, 10 Nov 2010 09:19:59 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Received: from [192.168.1.101] (76-220-56-223.lightspeed.sntcca.sbcglobal.net [76.220.56.223]) by asmtp016.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0LBO00HTKIU2L930@asmtp016.mac.com> for tcpm@ietf.org; Wed, 10 Nov 2010 09:20:27 -0800 (PST)
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1004200000 definitions=main-1011100104
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2010-11-10_06:2010-11-10, 2010-11-10, 1970-01-01 signatures=0
Message-id: <97C75EA8-6CC7-444C-A19D-370148B81918@mac.com>
From: rick jones <perfgeek@mac.com>
To: Hagen Paul Pfeifer <hagen@jauu.net>
In-reply-to: <20101110170017.GF5094@hell>
Date: Wed, 10 Nov 2010 09:20:23 -0800
References: <20101110152857.GA5094@hell> <804D02FE-39AF-4437-BB15-C2247842E120@mac.com> <20101110170017.GF5094@hell>
X-Mailer: Apple Mail (2.936)
Cc: tmrg <tmrg-interest@ICSI.Berkeley.EDU>, Matt Mathis <mattmathis@google.com>, tcpm <tcpm@ietf.org>
Subject: Re: [tcpm] Increasing the Initial Window - Notes
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2010 17:20:00 -0000

On Nov 10, 2010, at 9:00 AM, Hagen Paul Pfeifer wrote:

> * rick jones | 2010-11-10 08:33:30 [-0800]:
>
>> Do your customers run systems with support for TSO and/or LRO
>> enabled, or do they disable that today?  TSO can/may/will cause
>> 10*MSS or larger blobs of data to be injected into the network at one
>> time no?
>
> No, TSO does not change the packet behavior on the wire. At least no  
> CC
> related mechanisms. Packet spacing and stuff like that ignored here.

Earlier you wrote "New data are always pushed into the network in this  
quantum - a way to
much for the standard TCP CC mechanism to tune into a steady state for  
network
with a low BDP."  I read that as implying a concern about how much  
data any one connection injects into the network at any moment in time.

TSO does not change what any one packet looks like on the wire, but it  
certainly does change how many of them rush the wire at one time, yes  
bounded by cwnd - something those effectively infinite data sources  
like FTP will be pushing as far as it will go.  And depending on  
whether the stack receiving the LRO-stretched ACKs is counting bytes  
ACKed or number of ACKs the LRO can induce similar bursty behaviour.

>> And LRO can/may induce stretch ACK behaviour not unlike the
>> ACK avoidance heuristics of stacks such as those in HP-UX or Solaris.
>> What I've seen so far has suggested the goal is to get IW10 "blessed"
>> not to make IW10 mandatory.
>
> If the IETF "blessed" IW10 every vendor will enable it ...

And I presume, make it configurable.  It is already configurable on a  
per-route basis in the Linux stack.

rick jones
http://homepage.mac.com/perfgeek