Re: [tcpm] TCP tuning

Jerry Chu <hkchu@google.com> Wed, 03 February 2010 22:01 UTC

Return-Path: <hkchu@google.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 06E1E3A6A2C for <tcpm@core3.amsl.com>; Wed, 3 Feb 2010 14:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.477
X-Spam-Level:
X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
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 ZnUXknzNBSCF for <tcpm@core3.amsl.com>; Wed, 3 Feb 2010 14:01:19 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id D71413A6950 for <tcpm@ietf.org>; Wed, 3 Feb 2010 14:01:18 -0800 (PST)
Received: from spaceape8.eur.corp.google.com (spaceape8.eur.corp.google.com [172.28.16.142]) by smtp-out.google.com with ESMTP id o13M2191011259 for <tcpm@ietf.org>; Wed, 3 Feb 2010 14:02:01 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1265234522; bh=snlE0lehgK7B14k3fsGCif0CZco=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=xCPmL3Z4yeGDcTXy2AOrtHsojKSKFv9K2ldRTqMyMqyNzcpor3j7FSuzyE0iPkS9s Iik+1Q3c+7Tp8yU8BZbsg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=WZeluWLbi99U1u78OPA+VczTRKNe0JnI2FxmO4ycOAiCrgAUwEno18Ctb6VcPxs1y 9oMBCG1wGQ+A6yRFTJTmw==
Received: from pxi38 (pxi38.prod.google.com [10.243.27.38]) by spaceape8.eur.corp.google.com with ESMTP id o13M1x5V028795 for <tcpm@ietf.org>; Wed, 3 Feb 2010 14:02:00 -0800
Received: by pxi38 with SMTP id 38so1975176pxi.28 for <tcpm@ietf.org>; Wed, 03 Feb 2010 14:01:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.141.88.1 with SMTP id q1mr132148rvl.203.1265234503260; Wed, 03 Feb 2010 14:01:43 -0800 (PST)
In-Reply-To: <1e41a3231002031251v53f03f78x2ba6a12c4f12a22@mail.gmail.com>
References: <7BE9742D-6EDC-43FE-84FC-D22C52D23152@nokia.com> <1e41a3231002031232r6ec9edd3p6367dd9c2581fa08@mail.gmail.com> <d1c2719f1002031244g3415c8e1r7d36e26058158d20@mail.gmail.com> <1e41a3231002031251v53f03f78x2ba6a12c4f12a22@mail.gmail.com>
Date: Wed, 03 Feb 2010 14:01:43 -0800
Message-ID: <d1c2719f1002031401w5644e0e2hc380b6bb4e520827@mail.gmail.com>
From: Jerry Chu <hkchu@google.com>
To: John Heffner <johnwheffner@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: "tcpm@ietf.org WG" <tcpm@ietf.org>
Subject: Re: [tcpm] TCP tuning
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, 03 Feb 2010 22:01:20 -0000

On Wed, Feb 3, 2010 at 12:51 PM, John Heffner <johnwheffner@gmail.com> wrote:
> On Wed, Feb 3, 2010 at 3:44 PM, Jerry Chu <hkchu@google.com> wrote:
>> Hi John,
>>
>> On Wed, Feb 3, 2010 at 12:32 PM, John Heffner <johnwheffner@gmail.com> wrote:
>>> A couple thoughts:
>>> - A large initial window should probably only be used by mutual
>>> agreement.  Maybe via a TCP option during the handshake?
>>
>> This may not be needed. A receiver can effectively constrain the
>> sender's window by advertising a smaller initial receive window.
>>
>> Obviously this works for only the initial window, not the restart window.
>> (Oh, on a second thought this can be made to work for the restart
>> window too.)
>
> A good point, though most receivers (Linux 2.4 and later being the
> exception) advertise all available window space, not expecting a large
> initial burst from the sender.  I think you need a negotiation for
> opt-in rather than opt-out.

Yes, Linux 2.4 and later constrain its initial receive window per RFC3390,
making it harder for any future change to initcwnd to be deployed (i.e., both
sides' stack need to change). We're trying to fix this. See
http://www.spinics.net/lists/netdev/msg115912.html.

The change will also be useful for those hosts behind slow links for purposes
mentioned before.

Jerry

>
>  -John
>