From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 851BB200371 for ; Sat, 4 Feb 2012 17:57:22 -0800 (PST) Received: by wibhm2 with SMTP id hm2so6099890wib.16 for ; Sat, 04 Feb 2012 17:57:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=5aSjjv0beZspWD+gI5zs7IOUnMkJWcWhjiYnbtVLB5E=; b=ZGgcND2tkXYQKUMzx01aRzUHyJL6QMz8FEf6UfY7cw+smytavTAb/ZWC4Z7Uhy+34v /XSThf36ejLkgU2VlLr+/XJBeqGQi2HrDO1h8CSh97pmHxAEz1uln2uMo9pgj0FNUbfI iIXLSBeSivGxBNHFGPD8gffEVUvMvzuejdQX4= MIME-Version: 1.0 Received: by 10.180.106.33 with SMTP id gr1mr19755617wib.6.1328407040371; Sat, 04 Feb 2012 17:57:20 -0800 (PST) Received: by 10.216.50.194 with HTTP; Sat, 4 Feb 2012 17:57:20 -0800 (PST) In-Reply-To: <40C8C302-7B23-4272-8322-1D916BB0CEB2@gmail.com> References: <1325481751.2526.23.camel@edumazet-laptop> <4F046F7B.6030905@freedesktop.org> <40C8C302-7B23-4272-8322-1D916BB0CEB2@gmail.com> Date: Sat, 4 Feb 2012 17:57:20 -0800 Message-ID: From: "George B." To: Jonathan Morton Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: bloat Subject: Re: [Bloat] What is fairness, anyway? was: Re: finally... winning on wired! X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Feb 2012 01:57:23 -0000 On Sat, Feb 4, 2012 at 4:43 PM, Jonathan Morton wro= te: > There are two good things you can do. > > 1) Pressure your ISP to implement managed queueing and ECN at the head-en= d device, eg. DSLAM or cell-tower, and preferably at other vulnerable point= s in their network too. Well, if they have a Cisco network, that might work. Few other network gear vendors actively support ECN. > 2) Implement TCP *receive* window management. =A0This prevents the TCP al= gorithm on the sending side from attempting to find the size of the queues = in the network. =A0Search the list archives for "Blackpool" to see my take = on this technique in the form of a kernel patch. =A0More sophisticated algo= rithms are doubtless possible. Probably not something I want to use in production. Thanks, Johnathan. Now yet another question: Two different server configurations (these are real life examples, by the w= ay): 1. eth0 and eth1 bound as bond0 with vlans hanging off of them. Where to put the qdisc? On the bond interface? On the Ethernet interfaces? On the vlan interfaces? 2. eth0 and eth1 have vlan interfaces attached as eth0.10, eth1.10 and eth0.20, eth1.20. Those are bound to bond interfaces, bond10 and bond20. Same question, where best to apply the qdisc. George