From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 73C2421F245 for ; Fri, 21 Mar 2014 15:13:32 -0700 (PDT) Received: by mail-wi0-f178.google.com with SMTP id bs8so917594wib.17 for ; Fri, 21 Mar 2014 15:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=O9qg+EUgdS3r4+5hGs6XlAb6dNdMTFtBMwJqA0IKruc=; b=yeRtUJF6Bck7vLPDl5GfYeCpeMJQhcj0MxrinBUh5ixdUJFuFem8Jf/2Blf1Hub/ZJ JpSZoHxn+AjlgQiRjDpCte0EagZnLP5XrpelqqmYtHf72+l3DAN8PdJiLNjKx5OG7k2P yXLpUfitmYCXWr7Tf+rR4Pc0VOqfw51aRD3KTGeSrIszGzQAI6BvZO5zk61ZntAyvUV0 8VR4aGQ7U5N0Y5RLnm/UVuiPrtlD2zNlj4cydeC1XiRifi5/Kaez7LjriximfSEjJ2/p FzBAPlO1LKZVdpCeLtj2eGWYwOjpMFZuXRRHCID3MGOXgGjY62Ya9I8FDHmyS+UndneH Bd+w== MIME-Version: 1.0 X-Received: by 10.180.126.38 with SMTP id mv6mr45919wib.46.1395440010487; Fri, 21 Mar 2014 15:13:30 -0700 (PDT) Received: by 10.216.8.1 with HTTP; Fri, 21 Mar 2014 15:13:30 -0700 (PDT) In-Reply-To: <1395439222.9117.3.camel@edumazet-glaptop2.roam.corp.google.com> References: <20140318145221.GA31327@sesse.net> <07BD4518-2A7E-4F43-8978-791E3B2BDA2A@cisco.com> <87eh1wc05c.fsf@toke.dk> <87a9ckbz1q.fsf@toke.dk> <1395358884.9114.102.camel@edumazet-glaptop2.roam.corp.google.com> <1395414379.6441.17.camel@edumazet-glaptop2.roam.corp.google.com> <1395424311.8701.20.camel@edumazet-glaptop2.roam.corp.google.com> <1395439222.9117.3.camel@edumazet-glaptop2.roam.corp.google.com> Date: Fri, 21 Mar 2014 22:13:30 +0000 Message-ID: From: Dave Taht To: Eric Dumazet Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "Steinar H. Gunderson" , bloat Subject: Re: [Bloat] AQM creeping into L2 equipment 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: Fri, 21 Mar 2014 22:13:32 -0000 On Fri, Mar 21, 2014 at 10:00 PM, Eric Dumazet wro= te: > On Fri, 2014-03-21 at 18:08 +0000, Dave Taht wrote: > >> This is likely to have brutal effects on slow uplinks and uploads >> without pacing enabled. > > All I said was related to using fq/pacing, maybe it was not clear ? No, it was clear! Problem I was noting is that turning on sch_fq and setting the iw are not closely coupled so if you run iw20 without ensuring you are also running sch_fq, you are going to hurt a non-fq_codeled net... Apparently for some reason not everyone has made the switch yet. (and there were some other plausible side-effects from that 2000 paper on pacing worth checking up on) Are you ready to make sch_fq the default in 3.15? --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html