From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ww0-f47.google.com (mail-ww0-f47.google.com [74.125.82.47]) (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 EDD80200253 for ; Wed, 2 Nov 2011 03:31:14 -0700 (PDT) Received: by wwf22 with SMTP id 22so4458390wwf.28 for ; Wed, 02 Nov 2011 03:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-type:x-mailer:content-transfer-encoding:mime-version; bh=n6fA/F4bxdBt/Nx8FZC0F3gkGr2BIA6n4fPCCnVfrRA=; b=b3q4aPyMd0RrH4o/rMENQKNB0oEPpbxyRbtyhgi2BS2654JWd5RJiqbhn6/z9Xg7E3 4nvSjnI6ZGcnLyLR0u+HtjH1jJCXjIokDB+W5nb0oSmlbrBq0Av1Uct+DKRPRf23rh+I LKAKK0bZ6OOaHhyRho7UWzC/IWHrQm466s6jk= Received: by 10.216.171.202 with SMTP id r52mr1091632wel.93.1320229872875; Wed, 02 Nov 2011 03:31:12 -0700 (PDT) Received: from [10.150.51.212] (gw0.net.jmsp.net. [212.23.165.14]) by mx.google.com with ESMTPS id ei16sm3298920wbb.21.2011.11.02.03.31.10 (version=SSLv3 cipher=OTHER); Wed, 02 Nov 2011 03:31:11 -0700 (PDT) Message-ID: <1320229869.2292.5.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> From: Eric Dumazet To: David =?ISO-8859-1?Q?T=E4ht?= Date: Wed, 02 Nov 2011 11:31:09 +0100 In-Reply-To: <4EB115F7.5070203@gmail.com> References: <1319716772.2601.26.camel@edumazet-laptop> <1319731732.2601.40.camel@edumazet-laptop> <1319732832.2601.43.camel@edumazet-laptop> <4EB115F7.5070203@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.0- Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Cc: netdev@vger.kernel.org, Karel Rericha , bloat Subject: Re: [Bloat] Quick Fair Queue scheduler maturity and examples 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: Wed, 02 Nov 2011 10:31:15 -0000 Le mercredi 02 novembre 2011 à 11:05 +0100, David Täht a écrit : > (Example elided, see thread on netdev) > > On 11/02/2011 10:36 AM, Karel Rericha wrote: > > 2011/10/27 Eric Dumazet: > > Thanks for example Eric. But it only added more confusion to me now > > :-) I was under impression (and read somewhere) that QFQ is non work > > conserving scheduler so I can use it more or less like HTB or HFSC to > > set bandwidth constraints to flows. But from this example (and from > > sources/patches/papers I try not to pretend I fully understand) it > > looks to me like some multiqueue scheduler with arbitrary number of > > queues and ability to arbitrary assign flows to this queues. So some > > sort of fair division of available bandwidth to flows without > > arbitrary bandwidth caps to these flows. > This is what I want! It may not be what you want... > > I really dont see what is non work conserving here :-S Please save my > > soul and enlighten me because I am at dead end now :-) > > I initially had great hope for QFQ as I've been saying (mostly > privately) that "PFIFO_FAST must die" for over a year now. What to > replace it with is a rather large question, but I felt a start would be > to adopt some FQ algorithm. Over the last couple weeks I read all the > papers regarding DRR and QFQ and also poked into the source code and > like you, am seriously un-enlightened. > > I think eric's example is misleading as he divided up the queues by > bandwidth, rather than flow, in the first tier of his tc hierarchy. > useful as a test... It seems there is a bit of misunderstanding here. QFQ is not a 'all is included' in one qdisc, like SFQ You really need to setup qfq classes, and describe how packets are mapped to qfq classes (this is done by an external flow classifier) It also has no internal (default) flow classifier like SFQ did. It has of course no bandwidth constraints. If you need to shape and use QFQ, you'll have to use QFQ + a shaping qdisc. (This is why I used HTB in my script because I wanted to shape) If you dont need to shape, you still need to describe/setup qfq classes and chose appropriate flow classifier.